Browse the various statuses and the status call response in this section
Things to note
- The Get Status Service from PayGlocal is used to fetch the status of a transaction that was initiated using the GPI or Refund service.
- The Status service uses the GID returned in the GPI service response or
merchantUniqueIdthat was sent during the GPI or Refund Service request as a request parameter to fetch status of the transaction. - These API calls are always to be used in server to server communication channels.
- Utilise this API to verify the terminal status of transaction, once a form POST is executed on the merchant call back URL and control is returned back to the merchant.
Status Call Response
The response object of the "Transaction Status Check" API has an object with the key data which contains the status and meta data of the transaction whose status is being queried for. The data block has the following information contained within it:
| Data | Description |
|---|---|
| status | Status of the transaction. |
| detailedMessage | Detailed message returned after transaction completion. |
| transactionCreationTime | Time at which transaction was initiated (DD/MM/YYY HH:MM:SS). |
| gid | GID of the transaction. |
| Amount | Amount of the transaction during initiation. |
| Currency | Currency of the transaction during initiation. |
| merchantTxnId | Reference ID of transaction provided by the merchant. |
| reasonCode | PayGlocal defined Reason Code. |
Verifying your Transaction
SENT_FOR_CAPTURE and SENT_FOR_REFUND are successful statuses at PayGlocal.
The merchant is urged to utilise this endpoint to retrieve the status of the transaction and cross check the merchantTxnId and GID of the transaction with their internal records.
GPI Transaction Non-Final Status
| Status | Description | Next Action |
|---|---|---|
| INPROGRESS | GPI Service is executing the transaction. This status is returned when the merchant has loaded PayGlocal JS using the token returned in the GPI service response and the customer is executing the payment. This status can stay until the PayGlocal JS has timed out or the customer has closed the window of payment. | Wait for the customer to proceed with the payment flow. |
GPI Transaction Final Status
| Status | Description | Next Action |
|---|---|---|
| ABANDONED | This status highlights that the payment flow was abandoned by the consumer by either closing PayGlocal JS window or leaving the window to timeout. A reason for abandonment is also provided by PayGlocal to the merchant. | Create a payment link using PayGlocal and send it to the customer to pay at their own convenience. |
| ISSUER_DECLINE | Payment was declined by the card issuer. A decline reason will be provided. | Ask the customer to use another mode of payment. |
| SENT_FOR_CAPTURE | Payment was sent for capture by PayGlocal to the downstream acquirer. | Ship the goods. The payment can be refunded as required. |
| CUSTOMER_CANCELLED | Payment was cancelled by the customer on PayGlocal page. | Request the customer to pay again. |
| AUTHENTICATION_TIMEOUT | Payment was timed out on payment authentication page. | Request the customer to pay again. |
| GENERAL_DECLINE | Payment was declined by PayGlocal due to risk reasons. | Check customer profile & confirm customer identity. |
| REQUEST_ERROR | The Request has a field level issue. The client must fix the request fields and retry. | Retry after fixing the payload. |
| SYSTEM_ERROR | The PayGlocal system has issues. The client must try later. | Retry after some time. |
Refund Transaction Final Status
| Status | Description | Next Action |
|---|---|---|
| SENT_FOR_REFUND | Payment was sent for a refund on the merchant’s request. This status is received back when Get Status is requested for a Refund Service. | Ask for a return from the customer. |
| REQUEST_ERROR | The Request has a field level issue. The client must fix the request fields and retry. | Retry after fixing the payload. |
| SYSTEM_ERROR | The PayGlocal system has issues. The client must try later. | Retry after some time. |