Skip to main content
GET
/
pg
/
vba
/
{virtual_account_id}
/
payments
List VBA Payments
curl --request GET \
  --url https://api-pacb-uat.eximpe.com/pg/vba/{virtual_account_id}/payments/ \
  --header 'X-API-Version: <api-key>' \
  --header 'X-Client-ID: <api-key>' \
  --header 'X-Client-Secret: <api-key>' \
  --header 'X-Merchant-ID: <api-key>'
{
  "success": true,
  "message": "VBA payments retrieved successfully",
  "data": {
    "count": 138,
    "page": 1,
    "page_size": 250,
    "next": "https://api.example.com/pg/vba/a1b2c3d4/payments/?page=2",
    "previous": null,
    "results": [
      {
        "payment_id": "pmt_01HXYZABCDEF",
        "order_id": "ord_01HXYZABCDEF",
        "status": "CAPTURED",
        "amount": 12500,
        "payment_utr": "SBIN0123456789",
        "buyer_account_number": "1234567890",
        "buyer_ifsc": "SBIN0001234",
        "created_at": "2026-05-15T18:30:00.000000Z"
      }
    ]
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.eximpe.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
X-Client-ID
string
header
required

Client Application ID - Your unique application identifier used to authenticate API requests. You can find your Client ID in the Developer Settings section of the merchant dashboard.

​
X-Client-Secret
string
header
required

Client Secret Key - Your secret key used alongside the Client ID for secure authentication. Keep this confidential and never expose it in client-side code. Available in the Developer Settings section of the merchant dashboard.

​
X-Merchant-ID
string
header
required

Merchant Identifier - The unique ID for the merchant account. This is required for PSP (Payment Service Provider) merchants who manage multiple merchant accounts. You can find merchant IDs in the Merchant Management section of the dashboard.

​
X-API-Version
string
header
required

API Version - Specifies which version of the API to use (e.g., '1.X.X', '2.X.X', or '3.X.X'). This header allows you to control which API version your integration uses. Default version information is available in the Developer Settings.

Path Parameters

​
virtual_account_id
string
required

Virtual account ID of the VBA.

Query Parameters

​
page
integer
default:1

Page number for pagination.

Required range: x >= 1
​
page_size
integer
default:250

Number of items per page. Default is 250, maximum is 1000.

Required range: 1 <= x <= 1000
​
created_at_start
string<date-time>

Include payments with created_at >= value. ISO 8601 datetime, e.g. 2026-05-12T00:00:00Z.

​
created_at_end
string<date-time>

Include payments with created_at <= value. ISO 8601 datetime.

​
updated_at_start
string<date-time>

Include payments with last_updated_at >= value. ISO 8601 datetime.

​
updated_at_end
string<date-time>

Include payments with last_updated_at <= value. ISO 8601 datetime.

​
since_id
string

Cursor: payment_id of the last record already synced. Only payments created strictly after that one are returned. If since_id doesn't match a payment under this VBA, the API returns 400.

Response

VBA payments retrieved successfully

​
success
boolean
Example:

true

​
message
string
Example:

"VBA payments retrieved successfully"

​
data
object