Last updated
Last updated
You can perform recurring payments by just adding one additional parameter, recurringType
, to the payment request.
A recurring workflow consists of two phases:
without a cvv using a token previously stored during the initial payment.
During the initial payment, marked by the parameter recurringType
with the value INITIAL, the customer is present. Therefore, this initial request should contain additional parameters that authenticate the customer like card.cvv
for card payments.
COPYandPAY
Server-to-Server
In COPYandPAY you get this behaviour out of the box, so all you have to do is to follow the COPYandPAY Integration guide and add the following parameter to the /v1/checkouts request in :
Using the server-to-server integration, you have the option to append the parameter recurringType
to the initial /v1/payments request which also stores the card data:
Using the server-to-server integration, you have the option to append the parameter recurringType
to the initial /v1/payments request which also stores the card data:
For some cases you might want to use an alternative approach: If the shopper just registered his data without sending a payment at the same time, you would have sent his payment directly to the /v1/registrations endpoint as described here. In the same way as described above, the recurringType=INITIAL
parameter can be added to the request to indicate that this is the first in a series of recurring payments.
In the response of the initial transactions, the field “acquirerTxId9” will bring a parameter provided by the card scheme, to be used in the subsequent transactions using this card
Any payment request following the initial one must have the parameter recurringType
with the value REPEATED. This flag not only indicates that the request is part of a series of payments on this account, but also tells the payment system that no user is present and therefore the parameter card.cvv
is not part of the request. This fact in combination with the stored payment data of the registration greatly reduces the number of parameters of such a request:
To send the request of a repeated transaction, the field “customParameters[NTR]” must be filled with the information received previously in the initial one, in the field “acquirerTxid9", so the issuers can recognize the recurrency chain of the transaction