Update a Recurring PayIn Registration
This call can be used to modify parameters in the following scenarios:
- Reauthentication – Update the
CardId(card) orPaymentData(Apple Pay and Google Pay) if re-authentication is necessary (indicated by theStatusbecomingAUTHENTICATION_NEEDED). This must be followed by a CIT pay-in request. - User data change – Update
BillingorShippingif required - Recurrence ending – Set the
StatustoENDEDif the recurring payments have finished or will no longer be used
The existing registration’s PaymentType must match the request variant.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
If your platform is using a proxy to take SCA-triggering action on behalf of users, you also need to integrate mTLS authentication and use the api-mtls base URL.
Path parameters
The unique identifier of the recurring pay-in registration.
Request
Request body for updating a Card recurring pay-in registration (PaymentType CARD_DIRECT).
The existing registration's PaymentType must match the request variant. Updating the CardId requires re-authentication via a new CIT.
Request body for updating an Apple Pay recurring pay-in registration (PaymentType APPLEPAY).
The existing registration's PaymentType must match the request variant. Updating the PaymentData requires re-authentication via a new CIT.
Request body for updating a Google Pay recurring pay-in registration (PaymentType GOOGLE_PAY).
The existing registration's PaymentType must match the request variant. Updating the PaymentData requires re-authentication via a new CIT.
Request body for updating a PayPal recurring pay-in registration (PaymentType PAYPAL).
The existing registration's PaymentType must match the request variant.
Response
Response object for card recurring pay-in registrations.
Response object for PayPal recurring pay-in registrations.
Response object for Apple Pay recurring pay-in registrations.
Response object for Google Pay recurring pay-in registrations.