Back Office

Back Office vs Merchant Portal

Both the Merchant Portal and the Back Office have separate login pages and a distinctive user interface layout.

To make sure which one you are currently using, refer to these screenshots / login Urls.

Back Office

Merchant Portal

API key/secret configuration

Our Direct API's authentication mechanism is based on a API key/secret pair linked to your PSPID. Follow these steps: 

1. Login to the Back Office. Go to Configuration > Technical information > API settings > Direct API Key
2. If you have not configured anything yet, the screen shows “No api credential found”. To create both API Key and API Secret click on “GENERATE”

1. The screen now shows both codes in the table in the “Key” / “Secret” column respectively
   

If you wish to use a new API Key and API Secret, follow these steps

1. Select a period from the drop down menu “leave valid for X hour(s)”. Click on the “RENEW” button. The currently used API Key/Secret pair will expire after the date as defined in “Expiration date”
2. At the same time, a new API Key/Secret appears in the first line of the table. Make sure to save the API Secret in your system, as it will not be visible in the Back Office anymore once you access this menu anew
3. To force an immediate expiration of the expiring API Key/Secret, click on “EXPIRE”. Our platform removes the respective API Key/Secret from the table and our platform, making it unusable for requests

Webhooks key

Direct uses Webhooks to update your database about transaction results and status changes. Follow these steps: 

1. Login to the Back Office. Go to Configuration > Technical information > API settings > Webhooks Configuration
2. Click on "GENERATE WEBHOOKS API KEY" or enter the desired webhooks api key manually. The "WebhooksKey" is used to validate the messages as legitimate data transfer between our platform and your server. If you use one of our SDKs, this process happens automatically. If you choose to build your own application, make sure to include it
3. In "Endpoint URLs", enter your webhook destination(s) on your server. Enter any additional URL in a separate line
4. Click on "SAVE" to confirm your settings

1. To process the incoming webhooks in your system, you need to build an application on an HTTPS endpoint on your server. It should be able to

• Translate JSON into objects and signature verification. Our Server SDKs help you achieve this
• Respond to a GET action and echo the 'X-GCS-Webhooks-Endpoint-Verification' header value in the body
• Respond to the POST action with a 2XX status code for all events delivered
• Validate the signature on the message

Payment method activation status/configuration

The Back Office allows you to check and change the activation status of payment methods. Some payment methods require additional configuration depending on your preferences.

Payment method activation status

You can check the payment method’s activation status via Configuration > PM activation. You can change its activation status by clicking on the "Edit" symbol via PM activation.

Bancontact

Follow these steps to configure Bancontact for the Hosted Checkout Page. 

1. Go to Configuration > Payment methods > Bancontact > PM options > BCMC Mobile Application solution activation
2. Select the available payment modes your customers can choose from on the Hosted Checkout Page:
   

   Mode	Description
   Display QR code?	Allow your customers to pay by scanning a QR code.
   Display URL intent?	Allow your customers to pay with the Payconiq by Bancontact app.

3. Click on "Save" to confirm your choices
4. Depending on your choice, the following modes are now available for the respective devices:

   	Mobile	Tablet	Desktop
   QR code	No	Yes	Yes
   URL intent	Yes	Yes	No
   PAN Bancontact card	Yes	Yes	Yes

Bizum

You can activate Bizum in the following ways:

• In test with Direct simulator
• In test with end-to-end testing
• In live for real transaction processing

Activate in test account with Direct simulator

This allows you to send transaction requests to our test environment and perform test as described in our Testing chapter. These transactions do not have a financial impact.

Follow these steps:

1. Login to your test account. Go to Configuration > Payment methods > Choose new payment methods.
2. In "Additional filter criteria", go to "Web Banking". In the table, click on "Add" next to "Bizum".
3. In the "Contract data" tab, fill in the following properties:
   

   Property	Description/Actions
   UID	Enter any 8-digit numerical value.
   TID	Enter any 3-digit numerical value.
   Secret Key	Enter one of these SHA-256 SecretKey strings: VmFsaWRCaXp1bUtleUluMjRQb3MwMDAx Qml6dW1LZXlJbjI0UG9zMDAwMlZhbGlk S2V5SW4yNFBvczAwMDNWYWxpZEJpenVt SW4yNFBvczAwMDRWYWxpZEJpenVtS2V5 MjRQb3MwMDA1VmFsaWRCaXp1bUtleUlu UG9zMDAwNlZhbGlkQml6dW1LZXlJbjI0 MDAwN1ZhbGlkQml6dW1LZXlJbjI0UG9z

4. Click on "SUBMIT" to confirm.
5. Go to the "PM activation" tab. In "Activation", select the "Yes" radio button. Click on "SUBMIT" to confirm. 

Activate in test account with end-to-end testing

This allows you to send transaction requests to our test environment. Our platform sends your requests to the Bizum test environment to process your transactions. These transactions do not have a financial impact.

Follow these steps:

1. Login to your test account. Go to Configuration > Payment methods > Choose new payment methods.
2. In "Additional filter criteria", go to "Web Banking". In the table, click on "Add" next to "Bizum".
3. In the "Contract data" tab, fill in the following properties:
   

   Property	Description/Actions
   UID	Enter the 8-digit Unique Identifier you have received from Bizum.
   TID	Enter the 3-digit Terminal ID you have received from Bizum.
   Secret Key	Enter the SHA-256 SecretKey you have received from Bizum.

4. Click on "SUBMIT" to confirm.
5. Go to the "PM activation" tab. In "Activation", select the "Yes" radio button. Click on "SUBMIT" to confirm.

Activate in live for real transaction processing

This allows you to send transaction requests to our live environment. Our platform sends your requests to the Bizum live environment to process your transactions. These transactions have a financial impact.

Follow these steps:

1. Login to your live account. Go to Configuration > Payment methods > Choose new payment methods.
2. In "Additional filter criteria", go to "Web Banking". In the table, click on "Add" next to "Bizum".
3. In the "Contract data" tab, fill in the following properties:
   

   Property	Description/Actions
   UID	Enter the 8-digit Unique Identifier you have received from Bizum.
   TID	Enter the 3-digit Terminal ID you have received from Bizum.
   Secret Key	Enter the SHA-256 SecretKey you have received from Bizum.

4. Click on "SUBMIT" to confirm.