Create a Recurring PayIn (CIT)
Read more about the Recurring Card PayIn object →
Body parameters
Max. length: 255 characters
Custom data that you can add to this object.
For transactions (pay-in, transfer, payout), you can use this parameter to identify corresponding information regarding the user, transaction, or payment methods on your platform.
Required if the registration’s NextTransactionDebitedFunds
is empty.
The amount of the subsequent recurring pay-in. If this field is empty, the amount entered in the NextTransactionDebitedFunds
of the Recurring PayIn Registration is taken into account.
Caution: An amount must be transmitted during either the recurring registration or pay-in (if it’s different from the registration one).
Required if the registration’s NextTransactionFees
is empty.
The amount of the subsequent fees. If this field is empty, the amount entered in the NextTransactionFees
of the Recurring PayIn Registration is taken into account.
Caution: An amount must be transmitted during either the recurring registration or pay-in (if it’s different from the registration one).
Max. length: 255 characters
The URL to which users are automatically returned after 3DS2 if it is triggered (i.e., if the SecureModeNeeded
parameter is set to true
).
The language in which the payment page is to be displayed.
Max. length: 10 characters; only alphanumeric and spaces
Custom description to appear on the user’s bank statement along with the platform name. Different banks may show more or less information. See the Customizing bank statement references article for details.
Information about the browser used by the end user (author) to perform the payment.
The IP address of the end user initiating the transaction, in IPV4 or IPV6 format.
The unique identifier of the recurring pay-in registration.
Allowed values: VISA
, MASTERCARD
, CB
, MAESTRO
The card network to use, as chosen by the cardholder, in case of co-branded card products.
Responses
Was this page helpful?