• France
Search
Categories
Tags
English
French
English
Implementation
Embedded form (cards)
REST payment API
Hosted payment
Push mail
File exchange
Mobile payment
Logos
Plugins
Back office
Guides
Helpers
FAQ
Support

Prerequisites

Merchant server

For security reasons related to payments and in order to avoid fraudulent operations, the embedded form relies on a merchant server that must be provided by you.

This server responds to several needs:

  • Ensure that the transactions to be transmitted to the payment gateway correspond to purchases on your merchant website and that the amounts and currencies match.
  • Securely store your communication keys with the payment gateway.
  • Receive instant notifications from the payment gateway upon each payment event (accepted, rejected, etc.).

Merchant server

Embedded form (Browser),

Payment gateway server

Authentication keys

Three keys are needed for authenticating your exchanges with the payment gateway:

KEY DESCRIPTION
Server to server key For calls to Web Services.
JavaScript key For creating a payment form in the Buyer's browser.
Signature key In order to check the authenticity of the data returned to the IPN or during the return of the payment form in the browser.

Sign in to the Merchant Back Office

The keys are available in the Merchant Back Office. To access them, you must first connect to the Merchant Back Office. Users are identified with a login and password.

Finding the keys

You can retrieve your API keys and connection identifiers from the Merchant Back Office.

In the Settings > Shop menu, select your shop and go to the REST API keys tab.

This action is performed by a user who is authorized to manage keys and signing algorithms. Additionally, access to the REST API Keys tab requires specific functionality to be enabled. Please contact E-commerce customer service if you do not see this tab.

The tab contains all the information required for authentication:

Keep production password

As soon as the first payment is made with a real card, the production password is hidden for security reasons. We strongly advise you to keep this password in a safe place (encrypted file, database etc.). In case of loss, the merchant will have the option to generate a new one from his Merchant Back Office. As a reminder, the production password is visible in the Merchant Back Office from the Settings > Store > REST API Keys tab.

Keys of server to server calls

The REST payment Web Services use Basic HTTP authentication for securing the calls between the merchant server and the payment gateway servers (see Authentication phase for more information). In order to proceed to authentication, you need a login and a password.

They can be retrieved in the REST API Keys tab of the Merchant Back Office:

PARAMETER DESCRIPTION
User Username for building the header Authorization string.
Test password Password for building the header Authorization string for test transactions (with test cards).
Production password Password for building the header Authorization string for production transactions (with real cards).

For more information on the implementation, see Implementation using different programming languages.

The IPN signature is performed with the password. For more information, go here Use of IPN (notification URL).

I do not have an active account

If you do not yet have access to the Merchant Back Office, you can use demo key sets:

PARAMETER VALUE
Test user 73239078
Test password testpassword_SbEbeOueaMDyg8Rtei1bSaiB5lms9V0ZDjzldGXGAnIwH
Public test key 73239078:testpublickey_Zr3fXIKKx0mLY9YNBQEan42ano2QsdrLuyb2W54QWmUJQ
HMAC SHA256 test key VgbDd550wI6W1rwODGy56QAUkUQwIEdwXG5ziDUUC72BS
Base URL https://api.systempay.fr
URL for the JavaScript client https://static.systempay.fr/static/js/krypton-client/V4.0/stable/kr-payment-form.min.js

These keys are 100% functional. However, it is not possible to access the Merchant Back Office without having a personal account.

© 2023 | All rights reserved to Systempay
2.9.0-doc-1.8