Get Details for Processed Transaction
Retrieve a processed transaction’s details.
Authorizations
Most endpoints require an organization
token. Some endpoints require an application
token, and those endpoints are noted.
Path Parameters
ReferenceId for the transaction (PaymentId).
"45-as456777hhhhhhhhhh77777777-324"
Response
The name of the parent organization.
"PropertyManager Pro"
Paypoint's DBA name.
"Sunshine Gutters"
Paypoint's legal name.
"Sunshine Services, LLC"
Paypoint's entryname.
50
"d193cf9a46"
Unique Transaction ID.
"226-fe55ec0348e34702bd91b4be198ce7ec"
Connector used for transaction.
"gp"
Processor information, used for troubleshooting and reporting. This field contains a value when the API key used to make the request has management permissions.
"[MER_xxxxxxxxxxxxxx]/[NNNNNNNNN]"
Internal identifier used for processing.
"TRN_xwCAjQorWAYX1nAhAoHZVfN8iYHbI0"
Custom identifier for the transaction.
250
"O-5140"
Payment method used: card, ach, or wallet.
"ach"
Batch number.
"batch_226_ach_12-30-2023"
Batch amount.
30.22
Unique ID for customer linked to the transaction.
1551
InternalId for paypoint.
226
Transaction total amount (including service fee or sub-charge)
30.22
Net amount paid.
3762.87
Service fee or sub-charge applied.
1
Settlement status for transaction. See the docs for a full reference.
2
The transaction's operation.
"Sale"
The transaction's response data.
Custom identifier to indicate the transaction or request source.
100
"api"
Reference to the subscription that originated the transaction.
0
ID of immediate parent organization.
123
Identifier of refund transaction linked to this payment.
0
Identifier of return/chargeback transaction linked to this payment.
0
Not currently in use.
If applicable, the internal reference ID to the payment page capturing the payment.
0
Transaction date and time, in UTC.
"2025-10-19T00:00:00"
Service Fee or sub-charge transaction associated to the main transaction.
Split funding instructions for the transaction. The total amount of the splits must match the total amount of the transaction.
Events associated with this transaction.
The difference between the configured pass-through fee and the fee amount sent in the request. When transfering funds, Payabli uses this field to deduct the fee difference and transfer the correct amount to the merchant.
When a paypoint is set up to absorb fees, and the pass-through fee sent with the request is less than the configured amount, the difference must be covered by the merchant. See Fee Configuration to learn more about pass-through fee settings.
2
Identifier of registered cloud device used in the transaction.
"6c361c7d-674c-44cc-b790-382b75d1xxx"
Standard Entry Class (SEC) code is a a three letter code that describes how an ACH payment was authorized. Supported values are:
- PPD (Prearranged Payment and Deposit) - Used for credits or debits where an accountholder authorizes a company to initiate either a single or recurring transaction to their personal bank account. Common examples include direct deposit of payroll, mortgage payments, or utility bills. This is the default value for subscription payments.
- WEB (Internet-Initiated/Mobile Entry) - Used for debit entries when authorization is obtained from an accountholder via the internet or a wireless network. Common examples are online bill payments, ecommerce purchases, and mobile app payments where the consumer enters their banking information online.
- TEL (Telephone-Initiated Entry) - Used for one-time debit entries where authorization is obtained from a consumer via telephone. Common examples are phone-based purchases or bill payments where the consumer provides their banking information over the phone.
- CCD (Corporate Credit or Debit) - Used for fund transfers between business accounts. This code is specifically for business-to-business transactions. Common examples include vendor payments and other business-to-business payments.
The bank's accountholder type: personal or business.
personal
, business
Was this page helpful?