Endpoint : Recurring - Get Response
Recurring - Get Response
Upon a successful redirection to the merchant success or failure URL, you must used this transaction to get the result of the recurring web session. You must issue a RecurAck or RecurNACK to accept or refuse the token creation.
Request
Response
Related Articles
Endpoint : Recurring - Info Subscription
Recurring - Info Subscription This transaction is used to get information on a subscription Request Field Mandatory? CompanyNumber Y MerchantNumber Y Token Y ID Y OperatorID Y Response Field Mandatory? accountNumber amount avsStatus cardNumber ...
Endpoint : Recurring - Info User
Recurring - Info User This transaction is used to get all the available information on an existing Token in PayFacto vault. Request Field Mandatory? CompanyNumber Y MerchantNumber Y CustomerNumber Y Token Y OperatorID Y Response Field Mandatory? ...
Endpoint : Recurring - Info Invoice
Recurring - Info Invoice This transaction is used to get an information on an invoice generated from a subscription. Request Field Mandatory? CompanyNumber Y MerchantNumber Y InvoiceNumber Y OperatorID Y Response Field Mandatory? accountNumber amount ...
Endpoint : Recurring - Add User
Recurring - Add User This transaction is used to create a Token on PayFacto vault. The CardNumber parameter can be blank if you want to use PayFacto hosted token page. In that case, a token will be generated but not linked to any card number. You ...
Recurring Payments (Tokens)
dit Introduction The recurrent payment module allows to merchant to execute transactions according to criteria established with the client and without the presence of the cardholder. It also allows to automatically making payments at regular ...