POST
/
v2.01
/
{ClientId}
/
payins
/
recurring
/
card
/
direct

Read more about the Recurring Card PayIn object

Body parameters

Tag
string

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.

DebitedFunds
object

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).

Fees
object

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).

StatementDescriptor
string

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.

RecurringPayinRegistrationId
string
required

The unique identifier of the recurring pay-in registration.

Responses