Update Tokenized Payment Method
Updates a saved payment method.
Authorizations
Most endpoints require an organization
token. Some endpoints require an application
token, and those endpoints are noted.
Path Parameters
The saved payment method ID.
Query Parameters
When true
, enables real-time validation of ACH account and routing numbers. This is an add-on feature, contact Payabli for more information.
"true"
Body
Entrypoint identifier. Required for POST requests.
50
"d193cf9a46"
Refers to the payment page identifier. If provided, then the transaction is linked to the payment page.
50
"mypage-1"
Custom identifier to indicate the source for the request
100
"api"
Custom description for stored payment method.
"My card"
Information about the payment method for the transaction.
Object describing the Customer/Payor owner of payment method. Required for POST requests. Which fields are required depends on the paypoint's custom identifier settings. See PayorData Object Model for a complete reference.
When true
, if tokenization fails, Payabli will attempt an authorization transaction to request a permanent token for the card. If the authorization is successful, the card will be tokenized and the authorization will be voided automatically.
false
The amount for the fallbackAuth
transaction. Defaults to one dollar.
150
Response
Response body for payment method deletion.
Boolean indicating whether the operation was successful. A true
value indicates success. A false
value indicates failure.
true
Response text for operation: 'Success' or 'Declined'.
"Success"
The object containing the response data.
Was this page helpful?