The Sell Confirm API will be called by the Distributor post the Sell Verify API. On success, the value of gold for the particular transaction would be debited from the customer’s gold wallet.
Once the Sell Verify API is called by the Distributor, the Sell Confirm API needs to be called within 10 minutes from the time the Sell Verify API was called.
If the Distributor calls the Sell Confirm API post the time limit of 10 minutes from the time the Sell Verify API was called, the particular transaction would be Failed and the response in the Sell Confirm API would be rendered as Failed. (Status - 2 in Order Status API)
Note: Post the Distributor calls the Sell Verify API, Distributor can set a limit on Distributor’s side that the Sell Confirm API needs to be called within 8 minutes from the time the Sell Verify API was called.
Example: user_id = 2
|tx_id||This would be the Transaction ID which was passed by SafeGold in the previous Sell Verify API for the particular User ID.||Integer||Auto-incremental ID generated by safeGold system|
|date||Timestamp that needs to be considered for Reconciliation.||Y-M-D|
|invoice_id||Invoice ID generated by SafeGold which would be seen in the Invoice for the particular transaction.|
|Status Code||Code||Code Description|
|HTTP Status 400|
|1||Missing required information|
|2||Invalid transaction ID|
|3||User ID missing in transactions|
|7||Insufficient Gold Balance|
Once the Confirm API is successful, SafeGold will generate an Invoice. The Invoice will be accessible to the Distributor through an Invoice API. the Distributor will pass the transaction ID on the Invoice API and will receive a link to the Invoice in PDF Format.
Points to Remember
- The tx_id from the Sell Verify API must be passed as a parameter for this API for confirming the transaction associated to the tx_id.
- The tx_id is an important value for Sell Flow and must remain the same. Incase of any issue run the Sell Verify API again to initiate a new transaction.