Make a transaction
Make a single transaction. This method authorizes and captures a payment in one step. This is the v2 version of the api/MoneyIn/getpaid endpoint, and returns the unified response format. See Pay In unified response codes reference for more information.
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, 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 the Customer/Payor. Which fields are required depends on the paypoint’s custom identifier settings.
Recommended. The customer’s IP address. This field is used to help prevent fraudulent transactions, and Payabli strongly recommends including this data.
Response
Payabli’s unified response code. Starts with A (Approved) or D (Declined) followed by a four-digit code that provides specific details about the transaction result. See Pay In unified response codes reference for more information.
Human-readable reason corresponding to the response code.
Pagination token (equivalent to pageIdentifier in v1 APIs). Returns null when pagination is not applicable.
