List Batch Payments
GET/payment-batches
Retrieve batch payments that you have created.
Request
Query Parameters
An object ID that is used as a cursor in pagination. For instance, if you make a list request and receive 100 objects, ending with obj_foo42, your subsequent call can include after=obj_foo42 in order to fetch the next page of the list.
Possible values: >= 1
and <= 100
Default value: 10
A limit on the number of objects to be returned, between 1 and 100.
Possible values: [ASC
, DESC
]
Default value: DESC
Sort list objects in either ascending or descending order.
Responses
- 200
OK
Response Headers
Acme-Mode
string
Has the value LIVE if the data exists in live production mode or the value TEST if the data exists in test sandbox mode.
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
data
object[]
required
Unique identifier for the object.
Possible values: [ACT
, FAST
, PAYNOW
, TT
, MEPS
, GIRO
, MY_DUITNOW
]
Type of payment
The date payment should be sent.
The Acme-specific internal id of the source bank account.
Three-letter ISO 4217 currency code in full uppercase. Must be a currency supported by the payment type.
For example, FAST only supports SGD
.
Possible values: [OPEN
, PROCESSING
, SUBMITTED
, FAILED
, COMPLETED
]
Status of the batch
Time at which the object was created. In ISO 8601 format.
Time at which the object was last updated. In ISO 8601 format.
{
"data": [
{
"id": "bpmt_0FGDYHZMRZF49",
"type": "TT",
"paymentDate": "2024-12-31",
"senderAccountId": "intacc_0FGDYHZMRZF49",
"currency": "SGD",
"status": "SUBMITTED",
"createdAt": "2023-04-24T00:00:00.000000Z",
"updatedAt": "2023-04-24T00:00:00.000000Z"
}
],
"hasMore": true
}