Endpoint : Recurring - Delete User
Recurring - Delete User
This transaction is used to delete a Token and the linked card number.
Request
Response
Related Articles
PayFacto API - v1.0 - POST /v1/recur/InfoUser
POST /v1/recur/InfoUser Recurring — Info User Retrieves all available information on an existing Token stored in the PayFacto Token Vault. Use this endpoint to look up a subscriber's card details, subscription state, and billing history before ...
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 ...
PayFacto API - v1.0 - POST /v1/recur/DelSubscription
POST /v1/recur/DelSubscription Recurring — Delete Subscription Permanently deletes an active subscription from the PayFacto recurring billing module. Once deleted, all associated invoices will cease to be processed and the subscription cannot be ...
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 - 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 ...