Authorization
Example:
Authorization | Bearer Paste-Your-API-Key-HereQuery Parameters
Filter the list by transaction status (e.g.
settled).Filter transactions by a specific customer ID.
Filter by transaction type (e.g.
digital_product, event, membership).Filter transactions by a specific payment link ID.
Start of the date range to filter by (Unix timestamp in milliseconds).
End of the date range to filter by (Unix timestamp in milliseconds).
Comma-separated list of fields to include in each item.
Number of items to return per page. Defaults to
10, with a maximum of 50.Cursor for forward pagination. Pass the
nextStartingAfter value from the
previous response (a Unix timestamp in milliseconds, as a string) to fetch the
next page.Response
Successful ResponseMain Structure (Root)
Status code form API.
Status message that describes the status code.
List of transactions displayed.
Information on whether there is additional data to be retrieved (true/false).
Cursor to pass as
startingAfter to fetch the next page. null when there is
no further data.data Structure (Array Of Object)
Unique ID for the balance transaction history.
The amount of credit received from the transaction.
The status of the balance transaction (settled = completed/successful).
The type of transaction.
The payment method.
The unique ID of the customer who made the transaction.
The transaction creation time in epoch format (ms).
The transaction ID associated with the payment link.
Additional fees applied to the transaction (empty if none).
The ID of the payment link used.
The subscription ID (if the transaction is a subscription).
The Xendit transaction ID (if using the Xendit gateway).
Subscription details (if any).
Xendit transaction details (if any).
Object that stores transaction details related to the payment link.
Additional custom fields that can be filled in by the user (if any).
Customer data that makes transactions.
Payment link information used for transactions.
fee Structure (Array Of Object)
Unique ID for the fee entry.
The type of fee (e.g.
xendit_fee, mayar_fee).The fee amount deducted.
paymentLinkTransaction Structure (Object)
Payment link transaction ID.
Tracking URL data (if any).
Whether the admin fee is borne by the customer.
Whether the channel fee is borne by the customer.
customer Structure (Object)
Unique customer ID.
Customer’s name.
Customer’s email address.
Customer’s mobile phone number.
paymentLink Structure (Object)
ID payment link.
Payment link name.
