| Excerpt |
|---|
Version: 0.3 - Jan 2020 |
...
The following information must at least be registered in the iDIN QR back-end before the Merchant can use iDIN QR.
Elements to be received from Merchant/CPSP for registration at an iDIN QR back-end:
Data element | Description |
|---|---|
MerchantID | The iDIN MerchantID of Merchant, issued by the iDIN Acquirer. |
LegalName | The legal name of the Merchant, as registered with the Acquirer. |
Merchant API URLs | The URLs which the iDIN QR back-end uses to communicate to the Merchant. |
Contact name | Name of the person who can be contacted in the event of operational problems. |
Contact email | Email address of the contact person. |
Contact phone | Telephone number of the contact person. |
...
Data elements provided to a Merchant after successful registration for iDIN QR:
Data element | Description |
|---|---|
Merchant Token | A secret identification number specific to the Merchant which the iDIN QR back-end uses to identify and authenticate the Merchant. The Merchant must use this token to authenticate itself when generating iDIN QR code at the iDIN QR back-end. |
API URLs QR back-end | The API URL that the Merchant uses to communicate to the QR back-end for iDIN QR Generate API calls. |
Secret signing key | A secret symmetric key, created by the iDIN QR back-end with which the iDIN QR back-end must sign all its messages. The Merchant should validate the signature in the messages that it receives from the iDIN QR back-end by function of HMAC-SHA256(message body, secret key). |
...
Response Body Parameters
| Name | Description | Format |
|---|---|---|
| The IssuerAuthenticationURL of the Issuing Bank, received in the iDIN transaction response message from the Acquirer. | string |
| The iDIN TransactionID provided by the Acquiring Bank in the transaction response message of the standard iDIN protocol. | string |
...