Recurring payments without 3D Secure in the Mobile SDK

Modified on Mon, 24 Jul, 2023 at 3:58 PM

Tokenization using the mobile SDK is as easy as following the steps in our documentation available here: https://peachpayments.docs.oppwa.com/tutorials/mobile-sdk/prebuilt-ui/tokenization

Tokenization of card data is always 3D Secure authenticated.

One-click checkout in the mobile SDK will force 3D Secure on recurring/subscription payments unless the following steps are followed:

Add the following parameters to your payment request:
- standingInstruction.mode=REPEATED
- standingInstruction.source=MIT
- standingInstruction.type=UNSCHEDULED
Contact us ([email protected]) and notify us that you would like to bypass 3D Secure for all subsequent payments. We will update your merchant account configuration to allow this and provide you with a recurring entity ID.

Updated to this article - change of endpoint:

Environment	Current Domain	New Domain
Production	https://oppwa.com/	https://eu-prod.oppwa.com/
Customer Test (Staging)	https://test.oppwa.com/	https://eu-test.oppwa.com/

Once you have successfully completed the steps outlined above please ensure you have checked all your API calls to have updated/are using the new endpoint

FAQs around the Endpoint Change:

Are credit card tokens shared between oppwa.com and eu-prod.oppwa.com?
- Yes, this will have no impact on any tokens that have been created or any new tokens.
Is the same data shared between the two endpoints? ie. If we did a card authorisation on oppwa.com, would the capture succeed on eu-prod.oppwa.com? -
- Yes, the same data is shared and available.
Regarding transactions we see on BIP, is this data also shared between the two?
- Yes, it’s the same BIP and Console, there is no difference.

Deadline - End of June 2022 the current endpoint oppwa.com will be deactivated/redundant

https://peachpayments.freshdesk.com/a/solutions/articles/47001213445?portalId=47000077094