Close a batch manually

• A valid API key with admin or manager permissions — see Obtain API credentials
• At least one authorized or captured transaction in the current open batch

Batches close automatically at the end of each business day. Close manually when you need to:

• Settle transactions sooner — for example, at the end of a shift or event.
• Control settlement timing — align batch closure with your accounting schedule.
• Resolve issues — close a batch after reviewing and correcting transactions.

List batches to see the current open batch and its transaction summary.

curl -X GET \
  "https://api.dev.paradisegateway.net/v1/batches?take=5&sort_order=desc" \
  -H "APIKEY: YOUR-API-KEY"

Send PUT /v1/batches/status to close the current open batch.

curl -X PUT \
  https://api.dev.paradisegateway.net/v1/batches/status \
  -H "Content-Type: application/json" \
  -H "APIKEY: YOUR-API-KEY" \
  -d '{
    "status": "closed"
  }'

After closing, list batches again to confirm the batch status changed.

curl -X GET \
  "https://api.dev.paradisegateway.net/v1/batches/status?client_id=YOUR-CLIENT-ID" \
  -H "APIKEY: YOUR-API-KEY"

1. The processor receives all transactions in the closed batch.
2. Card transactions are submitted to the card network for clearing.
3. ACH transactions are submitted to the ACH network.
4. Funds are deposited to the merchant's account within 1–3 business days.
5. A new open batch is created automatically for subsequent transactions.

The GET /v1/batches endpoint supports the same pagination and sorting as transactions.

• List transactions with filters — view transactions within a batch
• About batch settlement — detailed settlement process
• Retrieve transaction details — check individual transaction status