Managing refunds is a critical part of the ACH lifecycle — especially when it comes to reconciling financial activity,
handling customer requests, and maintaining audit trails. The GrailPay ACH API provides a suite of endpoints to help
you retrieve and review refund activity across different levels of granularity: from batch summaries to individual
refund records.Whether you’re building a dashboard, troubleshooting a specific case, or simply auditing past refund activity, these
endpoints give you the visibility and flexibility you need to stay on top of refund flows.
You can retrieve a specific batch refund by using its unique UUID. This endpoint returns all key information for the
batch — including refund amount, status, processing timestamps, and linked transactions. This is useful when auditing or
reviewing the outcome of a large-scale reversal.For full details, refer to our OpenAPI documentation:
This endpoint allows you to fetch a list of all batch refunds, with support for filtering by status, date range,
and more. Results are paginated to support large datasets and can be sorted to help you find recent activity quickly.This is ideal for:
Reconciling large volumes of refund activity
Exporting historical refund records
Powering internal reporting dashboards
For full details, refer to our OpenAPI documentation:
To understand the full refund history for a particular transaction, use this endpoint to retrieve all refund objects
linked to a given transaction UUID. This helps teams confirm how much has been refunded, when, and in how many parts.This is especially helpful for:
Partial refunds
Multi-stage refund workflows
Auditing returned funds
For full details, refer to our OpenAPI documentation:
Use this endpoint to fetch a single refund by its UUID, giving you detailed insight into a specific refund’s amount,
status, related transaction, and any associated batch.This is useful for:
Troubleshooting issues with a specific refund
Confirming refund success
Displaying granular refund data in product interfaces
For full details, refer to our OpenAPI documentation: