Recurring

Use this checklist as an extension to our generic Go-live checklist if you’re going live with recurring payments. Refer to these steps to ensure a smooth and secure launch experience.

• Verify that the initial authorization flow (first payment) has been tested:

  • Checkout creation: make sure that your create recurring checkout passing the following parameter-value combinations: payment_channel: recurring, token_type: recurring

  • First charge: make sure you send the request with authentication_indicator: force_3ds in the first, initial charge

  • Subsequent payments (MITs): make sure you send the following to our payment/order endpoint: authentication_indicator: no_3ds , subscription_id and recurring checkout_id received in response to recurring checkout creation

    Subsequent payments: As the customer is not present and the initial charge has been authenticated, it is crucial not to request 3DS authentication in all subsequent MITs.

• Validate that PSP account settings allow for recurring or subscription-based payments

• If you are swapping an external token, make sure to use the correct value depending on the PSP you are swapping it from. Please refer to our API reference: swap an external token