Lost transaction information

This request will allow you to find out the status of the transaction search

Lost transaction information

get

Either order_id or custom_transaction_id must be set.

Authorizations

Query parameters

project_idnumberRequired

Project ID in the A-Pay system

Example: 1234567

order_idnumber · min: 16 · max: 16Optional

Deposit ID in the A-Pay system

Example: 0123456789abcdefPattern: ^[0-9a-f]+$

custom_transaction_idstring · min: 1 · max: 200Optional

Transaction ID in the client's system

Example: test_custom_id123

Responses

200

Success

application/json

400

Bad request

application/json

401

Unauthorized

application/json

404

Not found

application/json

get

HTTPcURLJavaScriptPython

GET /Remotes/lost-transaction-info?project_id=1 HTTP/1.1
Host: <domain>
apikey: YOUR_API_KEY
Accept: */*

{
  "success": true,
  "status": "Pending",
  "order_id": "0123456789abcdef",
  "custom_transaction_id": "test_custom_id123",
  "description": "text"
}

⚠️ Error Handling Guide

The following section describes possible error responses for the POST /Remotes/lost-transaction-info endpoint and how you can resolve them by yourself.

400 Bad Request – Validation Errors

When it happens:

• Neither order_id nor custom_transaction_id was provided

• Provided values are in an incorrect format (e.g., invalid length or pattern)

How to resolve it:

When the API returns a 400 Bad Request, it includes detailed information in the response body to help you identify what went wrong.

Make sure to inspect the following fields in the error response:

Field	Description
errors[].message	Describes the issue (e.g., "ensure this value has at least 16 characters")
errors[].location	Shows which parameter is invalid (e.g., ["order_id"])

401 Unauthorized

When it happens:

• The Authorization header is missing or contains an invalid API key

How to resolve it:

• Set the header: Authorization: Bearer YOUR_API_KEY

• Make sure the key has access to the specified project_id

404 Not Found – Transaction Not Found

When it happens:

• The specified order_id or custom_transaction_id does not match any existing lost transaction issue

How to resolve it:

• Confirm that the transaction ID you’re querying has actually been submitted previously

• Contact our support team if you're sure the lost transaction issue was created

• Create a new lost transaction issue if none is found