Authorize transaction
This endpoint is deprecated. New integrations should use the Authorize endpoint, then capture, void, or refund the resulting transaction with the corresponding endpoints. Transactions created with this legacy endpoint must be managed with the legacy lifecycle endpoints — they aren’t interchangeable with the current ones.
Authorize a card transaction. This returns an authorization code and reserves funds for the merchant. Authorized transactions aren’t flagged for settlement until captured.
Only card transactions can be authorized. This endpoint can’t be used for ACH transactions.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Long-lived API token sent in the requestToken header. See API token authentication.
Headers
Optional but recommended A unique ID that you can include to prevent duplicating objects or transactions in the case that a request is sent more than once. This key isn't generated in Payabli, you must generate it yourself. This key persists for 2 minutes. After 2 minutes, you can reuse the key if needed.
Query parameters
When true, the request creates a new customer record, regardless of whether customer identifiers match an existing customer. Defaults to false.
Request
Object describing the Customer/Payor. Which fields are required depends on the paypoint's custom identifier settings.
Response
Response text for operation: 'Success' or 'Declined'.
Boolean indicating whether the operation was successful. A true value
indicates success. A false value indicates failure.