Create a Recurring PayIn Registration

Register a series of recurring payment requests for the following payment methods (indicated by `PaymentType`): | PaymentType | Requires | Captured using | | --- | --- | --- | | `CARD_DIRECT` (default) | Tokenized `CardId` obtained from the card registration process. | [Create a Recurring Card PayIn (CIT or MIT)](/api-reference/recurring-card-payins/create-recurring-card-payin) | | `APPLEPAY` | Tokenized `PaymentData` object retrieved from the Apple Pay API. | [Create a Recurring Apple Pay PayIn](/api-reference/apple-pay/create-recurring-apple-pay-payin) | | `GOOGLE_PAY` | Tokenized `PaymentData` string retrieved from the Google Pay API. | [Create a Recurring Google Pay PayIn](/api-reference/google-pay/create-recurring-google-pay-payin) | | `PAYPAL` | No prerequisites. | [Create a Recurring PayPal PayIn (CIT or MIT)](/api-reference/paypal/create-recurring-paypal-payin) | <Note icon="fa-regular fa-circle-info"> **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](/api-reference/recurring-payin-registrations/update-recurring-payin-registration) object to create a new one with the same user. This restriction does not apply to other payment methods. </Note>

Authentication

AuthorizationBearer
Bearer authentication of the form `Bearer <token>`, where token is your auth token. If your platform is using a [proxy](/guides/sca/proxy-management) to take SCA-triggering action on behalf of users, you also need to integrate [mTLS authentication](/guides/sca/platform) and use the `api-mtls` base URL.

Path parameters

ClientIdstringRequired
Platform's API account identifier, associated with the API key.

Request

This endpoint expects an object.
CardobjectRequired

Request body for card recurring pay-in registrations, using a tokenized CardId.

OR
Apple PayobjectRequired

Request body for Apple Pay recurring pay-in registrations, using the tokenized PaymentData object retrieved from the Apple Pay API.

OR
Google PayobjectRequired

Request body for Google Pay recurring pay-in registrations, using the tokenized PaymentData string retrieved from the Google Pay API.

OR
PayPalobjectRequired

Request body for PayPal recurring pay-in registrations, redirecting the user to authenticate via PayPal.

Note that for PayPal:

  • Only one active PAYPAL registration object can exist for a user.
  • You can use NextTransactionDebitedFunds and NextTransactionFees in the registration (and therefore omit them from MIT pay-in requests). The RecurringType is always CUSTOM, and the FixedNextAmount parameter is not supported.
  • The FreeCycles property is not supported.

Response

Success
Cardobject

Response object for card recurring pay-in registrations.

OR
PayPalobject

Response object for PayPal recurring pay-in registrations.

OR
Apple Payobject

Response object for Apple Pay recurring pay-in registrations.

OR
Google Payobject

Response object for Google Pay recurring pay-in registrations.

Errors

400
Bad Request Error