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.).

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 Expert Back Office

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

1. Login to the Lyra Collect Back Office :

2. Enter your login.

3. Enter your password.

4. Click Login.

Finding the keys

In the Settings > Shop menu, select your shop and go to the REST API keys 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 Expert Back Office

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 Expert 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 computed with the password. For more information, go here Use IPN (notification URL) .

I do not have an active account

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

PARAMETER	VALUE
Test user	69876357
Test password	testpassword_DEMOPRIVATEKEY23G4475zXZQ2UA5x7M
Public test key	69876357:testpublickey_DEMOPUBLICKEY95me92597fd28tGD4r5
HMAC SHA256 test key	38453613e7f44dc58732bad3dca2bca3
Base URL	https://api.lyra.com
URL for the JavaScript client	https://api.lyra.com/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 Lyra Collect Back Office