Make transaction
Make a single transaction. This method authorizes and captures a payment in one step.
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 is not generated in Payabli, you must generate it yourself.
Value obtained from user when an API generated captcha is used in payment page
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.
When true
, the request creates a new customer record, regardless of whether customer identifiers match an existing customer. Defaults to false
.
Request
Object describing details of the payment. Required.
Information about the payment method for the transaction. Required and recommended fields for each payment method type are described in each schema below.
Custom identifier for payment connector.
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.
The entrypoint identifier.
Object describing an Invoice linked to the transaction.
Recommended. The customer’s IP address. This field is used to help prevent fraudulent transactions, and Payabli strongly recommends including this data.
Text description of the transaction.
Custom identifier for the transaction.
Custom identifier to indicate the transaction or request source.
Refers to the payment page identifier. If provided, then the transaction is linked to the payment page.
Payabli identifier of the subscription associated with the transaction.
Response
Ok
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.
Response text for operation: ‘Success’ or ‘Declined’.