string = 3 characters The three-letter ISO currency code (required, 3 characters).
Source required – object – The source of the payment (e.g., card, bank, etc).
typerequired
stringType of payment source
number
string
expiry_month
number
expiry_year
number
cvv
string
amount
number >= 0 The payment amount in the minor currency unit (e.g., cents). Omit or set to 0 to perform a card verification.
payment_type
string Default: “Regular” Enum:”Regular””Recurring””MOTO””Installment””PayLater””Unscheduled”The type of payment. Required for cardholder-not-present payments (e.g., mail/phone orders, MITs). For MITs, must NOT be “Regular”. Enum: “Regular”, “Recurring”, “MOTO”, “Installment”, “PayLater”, “Unscheduled”.
reference
string <= 80 characters A reference to identify the payment (e.g., order number). Max 80 chars. See Payfac docs for per-scheme limits.
description
string <= 100 characters A description of the payment (max 100 characters).
string <date-time> The date/time the payment was requested
amountrequired
integerThe original payment amount
currencyrequired
stringThe three-letter ISO currency code of the payment
statusrequired
string Enum:”Pending””Authorized””Card Verified””Voided””Partially Captured””Captured””Partially Refunded””Refunded””Declined””Canceled””Expired””Paid””Retry Scheduled”The status of the payment
approvedrequired
booleanWhether the payment was successful
_linksrequired
object >= 2 properties The links related to the payment
source
objectThe source of the payment
destination
objectThe destination of the payment
amount_requested
integer or nullThe full amount from the original authorization, if a partial authorization was requested.
payment_type
string or null Default: “Regular” Enum:”Regular””Recurring””MOTO””Installment””PayLater””Unscheduled”The payment type
payment_plan
object or nullThe details of a recurring subscription or installment
reference
string or nullYour reference for the payment
description
string or nullA description of the payment
expires_on
string or nullThe timestamp for when the authorization’s validity period expires
balances
object or nullThe payment balances
3ds
object or null3D Secure payment processing info
authentication
object or nullAuthentication info
risk
object or nullRisk assessment results
customer
object or nullThe customer to which this payment is linked
billing_descriptor
object or nullBilling descriptor
shipping
object or nullShipping details
payment_ip
string or nullThe IP address used to make the payment
sender
object or nullSender information
amount_allocations
Array of objects or nullThe sub-entities that the payment is being processed on behalf of
recipient
object or nullRecipient information
processing
object or nullProcessing data
items
Array of objects or nullOrder line items
metadata
object or null Additional metadata
property name*additional property any
eci
string or nullECI security level
scheme_id
string or nullScheme transaction identifier
actions
Array of objects or nullSummary of the payment’s actions
retry
object or nullAsync retry config
pan_type_processed
string or null Enum:”fpan””dpan”Type of PAN used for the payment
cko_network_token_available
boolean or nullIf Checkout Network Token was available
instruction
object or nullPayment instruction details
Object
idrequired
stringPayout unique identifier
requested_onrequired
string <date-time> The date/time the payout was requested
sourcerequired
objectThe source of the payout
destinationrequired
objectThe destination of the payout
amountrequired
integerThe original payout amount
currencyrequired
stringThe three-letter ISO currency code of the payout
reference
string or nullYour reference for the payout
billing_descriptor
object or nullDetails about the billing descriptor
statusrequired
string Enum:”Pending””Paid””Declined””Returned”The status of the payout
approvedrequired
booleanWhether the authorization was successful
sender
object or nullInformation about the sender of the payment’s funds
instruction
object or nullDetails about the instruction for payouts to bank accounts
_linksrequired
object non-empty Links related to the payouts
Object
idrequired
stringThe unique identifier for the payout.
requested_onrequired
string <date-time> The UTC date and time the payout was requested.
processed_onrequired
string or null <date-time> The UTC date and time the payout was approved or declined.
sourcerequired
objectThe source of the payout.
destinationrequired
objectThe payout destination.
amountrequired
integerThe amount to be paid out to the recipient.
currencyrequired
stringThe destination currency, as a three-letter ISO 4217 code.
statusrequired
string Enum:”pending””approved””declined”The status of the payout.
linksrequired
objectThe links related to the payment.
reference
string or null <= 50 characters An internal reference to identify the payout.
billing_descriptor
object or nullDetails about the billing descriptor.
sender
object or nullDetails about the payout sender.
scheme_id
string or nullThe scheme transaction identifier.
instruction
object or nullDetails about the instruction for the payout.
metadata
object or null A set of key-value pairs to attach to the payment.
Cancels an upcoming retry, if there is one scheduled. Cancellation requests are processed asynchronously. You can use workflows to be notified if the cancellation is successful.
Captures a payment if supported by the payment method. For card payments, capture requests are processed asynchronously. You can use workflows to be notified if the capture is successful.
Refunds a payment if supported by the payment method. For card payments, refund requests are processed asynchronously. You can use workflows to be notified if the refund is successful.
You can reverse a payment to return funds back to the customer, without having to manage the appropriate action to take based on the payment’s status.
Depending on the payment’s current status, requesting a payment reversal will automatically perform one of the following actions:
Fully refund a captured payment.
Void an authorized payment.
Cancel retries on a payment with pending retries.
Refund partially captured funds and void any remaining authorization amount.
Refund all captured funds from a partial refund and void any remaining authorization amount.
You can only request a payment reversal for card authorizations, captures, or an authorisation attempt that has a retry scheduled.
You cannot reverse a payment that has already been fully refunded, voided, or cancelled. If you attempt to do so, you’ll receive a 204 – No Content response code.
For card payments, reversal requests are processed asynchronously. You can use workflows to be notified when the reversal action completes. Note that the notification will depend on the reversal action taken; for example, for voided payments you will receive a payment_voided notification, and so on.
The reversal request will be rejected with a 403 – Forbidden response code if the payment cannot be reversed. This may happen if:
the payment is not a card payment
the payment is not authorized and is still in the process of 3D Secure (3DS) authentication
Search and filter through your payment data to retrieve payments that match your query.
If a search returns more results than the value specified in limit, additional results are returned in a new page. A link to the next page of results is returned in the response’s _links.next.href field.
For more information on search syntax, see the Search and filter payments documentation.
Returns a list of your business’ payments that match the specified reference. Results are returned in reverse chronological order, with the most recent payments shown first.