-
- abort-payment-on-terminal
- capture-payment
- filter-payments
- find-payment
- initiate-payment-flow
- list-activity-logs
- list-payment-activities
- list-payments
- list-payments-by-contact
- list-payments-by-terminal
- refund-payment
- request-payment
- resume-payment-on-terminal
- retrieve-refund-performance
- retrieve-sales-performance
- reverse-payment
- start-payment-on-terminal
- void-payment
Find an invoice
Retrieve details about a specific invoice in your merchant account.
invoice_id
string
Required. The unique identifier of the invoice to retrieve.
| Attribute | Description |
|---|---|
invoice_idstring
|
Always present. The ID of the invoice. |
numberstring
|
Always present. The full number of the invoice. |
statusstring
|
Always present. The status of the invoice. Possible values:
|
amountnumber
|
Always present. The gross amount of the invoice in subunits. |
net_amountnumber
|
Always present. The net amount of the invoice in subunits. |
vat_amountnumber
|
Always present. The VAT amount of the invoice in subunits. |
currencystring
|
Always present. The 3-letter ISO currency code (e.g., 'THB'). |
issued_onstring
|
Always present. The date the invoice was issued in ISO 8601 format. |
pdf_download_urlstring
|
Nullable. The URL to download the invoice PDF. |
receipt_idstring
|
Nullable. The ID of the receipt associated with this invoice. |
receipt_numberstring
|
Nullable. The full number of the receipt associated with this invoice. |
receipt_pdf_download_urlstring
|
Nullable. The URL to download the receipt PDF. |
receipt_created_atnumber
|
Nullable. The creation timestamp of the receipt (Unix timestamp). |
created_atnumber
|
Always present. The creation timestamp (Unix timestamp). |
NOT_FOUND
This error occurs when no invoice with the provided ID exists in your merchant account. Double check that you're using the correct invoice ID.
UNHANDLED_ERROR
This error occurs when the server encounters an unexpected internal error that it cannot handle gracefully. This typically happens due to bugs, infrastructure issues, or edge cases that weren't anticipated during development.
INVALID_ARGUMENTS
This error occurs when the request contains invalid or missing parameters. Common cases include missing required fields, or values that don't match the expected format or type.
BAD_VERSION
This error occurs when making requests to an API version that does not exist. This commonly happens when using an outdated SDK or when the API version specified in the request URL is incorrect.
