Third Party App Return Signature
Description¶
Returns a SHA-256 signature generated using the merchant code, merchant secret key, current GMT date, and invoice number. The generated signature can be included as a URL parameter in the third-party application's return URL.
Request¶
Endpoint
/v2/thirdPartyAppReturnSignature
Method
GET
Attributes
| ELEMENT | DESCRIPTION | FORMAT |
|---|---|---|
| merchantCode | Required Unique identifier assigned to the merchant. Used to retrieve the merchant-specific secret key and generate the signature.. |
e.g., abc-defgh |
| invoiceNumber | Required Invoice number associated with the transaction. If not provided, an empty value is used when generating the signature. |
e.g., 123456789 |
Signature Generation:
Given all the details as above, the request Endpoint would appear as follows:
<BASE_URL>/v2/thirdPartyAppReturnSignature?merchantCode=ABC123&invoiceNumber=123456789
Note
BASE_URL is derived from the merchant code.
For Test Environment, to obtain the BASE_URL, please contact vela@datumtg.com.
For Production Environment, to obtain the BASE_URL, please contact vela@datumtg.com.
Response¶
The Response contains the generated signature.
{
"signature":"c23134e276c219f812087b6912ba52911cad7b089f2175aef3ef027f366261d2"
}
| ELEMENT | DESCRIPTION | FORMAT |
|---|---|---|
| signature | The Signature is SHA-256 of (merchantCode : merchantSecretKey : DateInGMT : invoiceNumber). | The date is generated by the system using the current date in GMT and the format: yyyy-MM-dd |
Updated As Of Version 7.2.x