Post calling the ​ Confirm API (Buy/Sell/Delivery/Gifting), ​ the Distributor will call the ​ Order Status API ​ irrespective of the status received in the respective API’s to double confirm the status of the transaction on SafeGold’s system

The status of the ​ Order Status API ​ needs to be considered as the final status of the particular transaction.

0​ corresponds that the status of the transaction is ​ Pending. ​ There may be two scenarios in this -

  1. If the ​Verify API​ has been hit and the Confirm API​​ has not been hit, then the status would be Pending.
  2. If the ​Confirm API​​ has been hit and there is a delay in the response, and the Order Status API is hit during the delay, then the status would be Pending.

1 corresponds that the status of the transaction is Success and the gold was credited/debited to the customer’s wallet balance.
2 corresponds that the status of the transaction is ​Failed.

Scenarios for Confirm API -

1st Scenario: Distributor has hit the Confirm API and it is successful

On the success of the Confirm API, ​ SafeGold will send successful parameters in the Confirm API with the HTTP Status as 200 and Invoice ID in the response.

2nd Scenario: Distributor has hit the Confirm API and it is Failed

On Failure of the ​ Confirm API, ​ SafeGold will send ​ BLANK RESPONSE ​ in the Confirm API with the HTTP Status as 200. Distributor will hit the ​ Order Status API ​ to confirm the status is ​ 2. ​ Distributor will receive Failure in Status API when the Confirm API is called post 10 minutes from the time Verify API was initiated.

  1. For Buy and Delivery Transactions:
    When Distributor receives a Failure Response, the Distributor will reverse the amount for the particular transaction that was paid by the customer.
  2. For Sell Transactions:
    When the Distributor receives a Failure Response, the Distributor won’t settle the amount for the particular transaction to the customer.

3rd Scenario: Distributor has hit the Confirm API and there is a delay in receiving the response or there has been an unpredicted response sent in the Confirm API.

In this scenario, post hitting the ​ Confirm API, ​ Distributor will hit the ​ Order Status API ​ for the particular transaction. If the status in the ​ Order Status API ​ is 0 - Pending, Distributor will again hit the ​ Confirm API ​ and continue the process of hitting the ​ Order Status API ​ up to 10 mins from the initiation of the Verify API. Within 10 minutes, if the Distributor receives the order status as ​ 1 - Success or ​ 2- Failure, ​ the Distributor will follow the process as mentioned in Scenario 1 and Scenario 2. After 10 minutes if the ​ Confirm API ​ is called, the Order Status API ​ will return a Failure response as it exceeds the limit of 10 minutes between the ​ Verify API ​ and ​ Confirm API.