Paystrax company logo
Copy & Pay Integration

Copy & Pay Integration Guide

Easy steps to integrate checkout via Copy & Pay solution.

Documentation Access to Gateway Portal Credentials Integration Points Webhooks Refunds & Reversals

Documentation

Integration steps

The integration has 3 steps:

  • Prepare checkout
  • Create the Payment Form and display to the user
  • After redirect – get the payment status

For testing purposes use eu-test.oppwa.com (not test.paystrax.net) URL to send transactions.

For production use eu-prod.oppwa.com.

Access to Gateway Portal

These are the links to our Gateway Portal:

To get access to Gateway Portal, the merchant needs to confirm the first/last name and personal corporate email of each person who needs to be granted access.

Credentials

It is possible to start with credentials from the documentation where entityID and Bearer Token is used:

curl
curl https://eu-test.oppwa.com/v1/checkouts \
 -d "entityId=8ac7a4c86a304582016a30b41682019b" \
 -d "amount=92.00" \
 -d "currency=EUR" \
 -d "paymentType=DB" \
 -d "integrity=true" \
 -H "Authorization: Bearer OGFjN2E0Yzg2YTMwNDU4MjAxNmEzMGI0MTZlMjAxOWZ8QmJkdXdacGg5TUhMbTV0dzplbkw="

We can provide credentials specific to the integrator, including login to the portal (in our Gateway Portal you can access real-time information about authorised and rejected transactions. There you can void and refund transactions.). Integrator needs to let us know who should receive the credentials for the integration and to the portal.

Integration Points

Integrating for test transaction

When integrating for test transactions you need to use 3DS Simulator and test cards: 3DS Test Cards | Developer Portal.

Simplest way is to use payment type DB (one step payment and capture) in your integration.
It is possible to use two step payments with payment type PA and Backoffice operation CP to capture the payment. Tutorial can be found here.

  • Change look and feel of the iFrame
  • Change look, feel and translations

If a customer leaves, it will take 30 minutes for the session to time out.

Include merchantTransactionId parameter: Merchant provided reference number, should be unique for your transactions. This identifier is often used for reconciliation.

For a more successful 3DS include: https://docs.paystrax.net/tutorials/threeDSecure

Both entityId and Token is unique per merchant.

Pending Transaction Status Codes (non-final):
https://docs.paystrax.net/reference/resultCodes
See (/^(300.100.100)/ – Soft Decline) + (/^(000.200)/. = Result codes for pending transactions)

Webhooks

  • Integrator provides an endpoint URL and e-mail for notifications of webhook errors.
  • We need to register URL for you to use it [URL must accept a registration call].
  • Webhooks only work if the user presses to PAY.
  • Webhooks retry for 30 days to deliver the response.

For getting unique values sent back in the webhooks that you would need to find the original order or transaction in your system, use the customParameters in your request and they will be returned by the webhook. Example customParameters[myKey]=myValue will be returned in the webhook as “customParameters”:{“SHOPPER_myKey”:”myValue”}

Refunds & Reversals

  • The gateway collects transactions in a 24-hour window that ends at 22:30.
  • Reversals can be done only within that time, refunds must be done after that time.
  • Refunds have a higher cost, and it is slower to reach the cardholder.

Full information can be found here.