Bill-Payment Status and Reconciliation
Use your original purchase reference to retrieve the latest status. This is the safe way to handle a 202 pending response, a client timeout, or an interrupted connection.
Get one bill payment
GET https://backendapi.sayswitchgroup.com/api/v1/bills/history/{reference}
curl --request GET \
--url "https://backendapi.sayswitchgroup.com/api/v1/bills/history/merchant-order-10001" \
--header "Authorization: Bearer YOUR_SECRET_KEY" \
--header "Accept: application/json"The secret key determines both the merchant and environment. A test key cannot retrieve a live transaction, and a live key cannot retrieve a test transaction.
List recent bill payments
GET https://backendapi.sayswitchgroup.com/api/v1/bills/history
This endpoint returns up to the 50 most recent bill payments for the authenticated merchant and environment.
curl --request GET \
--url "https://backendapi.sayswitchgroup.com/api/v1/bills/history" \
--header "Authorization: Bearer YOUR_SECRET_KEY" \
--header "Accept: application/json"Reconciliation rules
- Treat
deliveredas the final successful state. - Treat
failedas the final failed state. - Keep polling
pendingwith a reasonable delay; do not submit the purchase again. - Always reconcile using your original
reference. - SaySwitch sends a final webhook when an initially pending purchase becomes delivered or failed. You can use this endpoint while waiting for that notification.
See Bill-payment webhooks for the final-status payload.