Create a Recurring PayIn Registration
Register a series of recurring payment requests for the following payment methods (indicated by PaymentType):
Note – Only one registration per user on PayPal
On PayPal, only one recurring pay-in registration can be used per UserId. You can end a user’s existing registration object to create a new one with the same user.
This restriction does not apply to other payment methods.
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
Request
Request body for card recurring pay-in registrations, using a tokenized CardId.
Request body for Apple Pay recurring pay-in registrations, using the tokenized PaymentData object retrieved from the Apple Pay API.
Request body for Google Pay recurring pay-in registrations, using the tokenized PaymentData string retrieved from the Google Pay API.
Request body for PayPal recurring pay-in registrations, redirecting the user to authenticate via PayPal.
Note that for PayPal:
- Only one active
PAYPALregistration object can exist for a user. - You can use
NextTransactionDebitedFundsandNextTransactionFeesin the registration (and therefore omit them from MIT pay-in requests). TheRecurringTypeis alwaysCUSTOM, and theFixedNextAmountparameter is not supported. - The
FreeCyclesproperty is not supported.
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.