POST
/
MoneyIn
/
authorize
curl --request POST \
--url https://api-sandbox.payabli.com/api/MoneyIn/authorize \
--header 'Content-Type: application/json' \
--header 'requestToken: <api-key>' \
--data '{
"entryPoint": "f743aed24a",
"ipaddress": "255.255.255.255",
"paymentMethod": {
"initiator": "payor",
"cardHolder": "John Cassian",
"cardzip": "12345",
"cardcvv": "123",
"cardexp": "02/25",
"cardnumber": "4111111111111111",
"method": "card"
},
"paymentDetails": {
"totalAmount": 100,
"serviceFee": 0
},
"customerData": {
"customerId": 4440
}
}'
{
"responseText": "Success",
"isSuccess": true,
"pageIdentifier": null,
"responseData": {
"authCode": "123456",
"referenceId": "227-d30f8a47ddaf4fa989016d21d088ae5b",
"resultCode": 1,
"resultText": "Approved",
"avsResponseText": "No address or ZIP match only",
"cvvResponseText": "CVV2/CVC2 no match",
"customerId": 1409,
"methodReferenceId": null
}
}

Authorizations

requestToken
string
header
required

Most endpoints require an organization token. Some endpoints require an application token, and those endpoints are noted.

Headers

idempotencyKey
string

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.

Example:

"6B29FC40-CA47-1067-B31D-00DD010662DA"

Query Parameters

forceCustomerCreation
boolean
default:false

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.

Response

200
application/json

Ok

General response for certain moneyIn and moneyOut endpoints.