Please visit opayo.co.uk for more information and to register.
Here's what you need to do to start testing your integration and to go live with Opayo:
54.243.60.3
54.152.220.165
255.255.255.255
As soon as your testing is complete and your acquiring bank has confirmed your Merchant ID, your account will automatically be set to Live. Opayo will let you know when this has happened. You can then complete the final steps of integration:
54.243.60.3
54.152.220.165
255.255.255.255
Are you selling subscriptions or completing transactions on behalf of customers? This additional configuration needs to be completed
If you plan to process transactions where the customer will not be present, such as with subscriptions or with a store administrator using the Unified Order Entry password to checkout as the customer, then there is an additional configuration step that you need to complete.
Specifically, to allow for these customer-not-present transactions to complete without requiring 3D Secure, Foxy needs to process the purchase as what's called an MIT (Merchant Initiated Transaction). Opayo requires that we complete that using a Continuous Authority account type - which signifies that the transaction is being processed with an existing authority from the customer.
Continuous Authority isn't always automatically enabled for your merchant account and your Opayo account though, so you will need to confirm with both your merchant account provider (usually your bank) and with Opayo support if your account has “Continuous Authority” enabled. If not, they will be able to assist you with getting it enabled with your merchant account provider and Opayo.
Failing to ensure your merchant and gateway accounts have Continuous Authority enabled will result in any transactions not initiated by the customer to error.
For Opayo, the prepayment webhook will be sent to your endpoint twice; once before the 3D Secure challenge, and once before the payment is attempted. You can identify the different triggers using the Foxy-Webhook-Event
header values of validation/3ds
and validation/payment
.
You can decline the transaction from either trigger, but there are optional additional values you can return with a true
response to alter how the 3D Secure challenge occurs with Opayo. Specifically you can pass an additional top level object in the response that looks like this:
"overrides": { "opayo": { "apply_3dsecure": 2, "threeds_exemption_indicator": "05" } }
The values for apply_3dsecure
and threeds_exemption_indicator
match up to the Apply3DSecure
and ThreeDSExemptionIndicator
attributes as described within Opayo's documentation here. Consult with Opayo support for the best values to use for your specific requirements.
Contact Opayo for info. Know more? Feel free to edit this page with info.
Sage Pay v. Sage Payment Solutions Sage Payment Solutions (now called Paya) is different than Sage Pay (now called Opayo). Make sure you are sure which Sage solution you use if you're familiar with their old names, and always make sure to test before you assume things are working as expected.
If you have tips, experience, or helpful notes related to this gateway that would benefit others, please add them below, including your name and the date. We reserve the right to edit or remove comments that don't add value to this page.