Endpoint : 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 must create a Recurring - Session to get a web SecureID to have the card number entered directly on PayFacto web pages.
Related Articles
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 ...
Endpoint : Recurring - Add Subscription
Recurring - Add Subscription This transaction is used to add a new subscription to CT-Payment recurring schedule. At the request moment, the payment will be process using the token provided. Request Field Mandatory? CompanyNumber Y MerchantNumber Y ...
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 - Delete User
Recurring - Delete User This transaction is used to delete a Token and the linked card number. Request Field Mandatory? CompanyNumber Y MerchantNumber Y CustomerNumber Y Token Y OperatorID Y Response Field Mandatory? accountNumber amount avsStatus ...
Endpoint : Recurring - Modify User
Recurring - Modify User This transaction is used to modify information linked to a Token. When the value "**NO_CHANGE**" is sent in the CardNumber field along with the new expiry date, only the expiry date will be updated on our Token vault. Request ...