Authorize Transaction
Authorize a card transaction. This returns an authorization code and reserves funds for the merchant. Authorized transactions aren’t flagged for settlement until captured.
Note: Only card transactions can be authorized. This endpoint can’t be used for ACH transactions.
Authorizations
Most endpoints require an organization
token. Some endpoints require an application
token, and those endpoints are noted.
Headers
A unique ID you can include to prevent duplicating objects or transactions if a request is sent more than once. This key is not generated in Payabli, you must generate it yourself.
Query Parameters
When true
, the request creates a new customer record, regardless of whether customer identifiers match an existing customer.
Body
Model request body for Authorize Transaction.
The entrypoint identifier.
50
Object describing payment method to use for transaction.
Custom identifier for payment connector.
250
Object describing the customer/payor. Which fields are required depends on the paypoint's custom identifier settings. See PayorData Object Model for a complete reference.
Text description of the transaction.
250
Custom identifier for the transaction.
250
Details about the payment.
Custom identifier to indicate the transaction or request source.
100
Refers to the payment page identifier. If provided, then the transaction is linked to the payment page.
50
Payabli identifier of the subscription associated with the transaction.
Response
General response for certain moneyIn and moneyOut endpoints.
Boolean indicating whether the operation was successful. A true
value indicates success. A false
value indicates failure.
Auxiliary validation used internally by payment pages and components.
The object containing the response data.
Response text for operation: 'Success' or 'Declined'.
Was this page helpful?