PayPlug

📘
Who should use this guide
This guide is intended for merchants who:

Use Payrails as a payment orchestrator

Use PayPlug to accept card payments in EUR

PayPlug is a server-to-server card connector running on the Dalenys (ex-Be2bill) gateway — there is no hosted payment page. Your shopper enters their card details directly in your checkout, and is only redirected to complete a 3DS challenge, when one is required.
Note: PayPlug only supports EUR.

Create and configure a PayPlug integration in Payrails

Following are the initial steps to set up PayPlug:

Log in to the Payrails portal.
Go to Settings → Integrations → Payments.
Select Add instance to create a new PayPlug integration configuration.
Select the workspaces where this integration should be available.

About workspaces

Workspaces determine where this integration is available. They let you isolate provider setups by region or business line, or share the same configuration across multiple workspaces.

Step 2: Choose the provider

Select PayPlug and continue to the next step.

Step 3: Configure your PayPlug integration

📋
What you'll need from PayPlug
PayPlug supports two credential modes, both configurable on the same provider config. You can set up either or both:

Payrails 3DS (external 3DS) — optional. An Account ID and Account key (secret) issued for external/Payrails-managed 3DS.

PayPlug 3DS (provider-managed 3DS) — optional. A separate Account ID and Account key (secret) issued for PayPlug-managed 3DS.

⚠️ At least one of the two modes must be configured for the integration to process payments.

Integration instance name

An integration instance is a specific payment provider setup in Payrails. You can create multiple instances for each provider based on region, currency, or business needs. Choose a clear, consistent name, as it is used in routing.

In Payrails

Enter an Instance name for your integration.

Payrails 3DS credentials (optional)

In Payrails

Enter the Account ID and Account key provided by PayPlug for external (Payrails-managed) 3DS.

ℹ️
The connector uses these credentials whenever the authorize request carries complete external 3DS data. If external 3DS data isn't present, it falls back to the PayPlug 3DS credentials below (if configured).

PayPlug 3DS credentials (optional)

In Payrails

If you also want provider-managed 3DS available, enter the separate Account ID and Account key issued by PayPlug for this mode.

🔒
Store your account keys securely. They're used to sign every request and to verify that notifications genuinely come from PayPlug.

Payment methods

In Payrails

Under Payment methods, enable Card.

Configure notifications

PayPlug (Dalenys) sends form-encoded callbacks to a notification URL you configure on the PayPlug/Dalenys side.

In Payrails

After saving your PayPlug configuration, copy the generated notification URL from the provider config.

In PayPlug (Dalenys back office)

Paste the Payrails notification URL into your notification settings.

PayPlug will POST form-encoded callbacks (transaction ID, operation type, execution code, amount, currency, order ID, etc.) to this URL. Payrails verifies the request signature and responds HTTP 200 "OK".

Enable the integration

In Payrails

Select Save account to save the configuration and enable the integration.
The Enabled status confirms that the PayPlug integration is active.

Your PayPlug integration is now ready to process payments.

Next steps

Run a test payment in test mode using a PayPlug test card, in EUR:

Frictionless: Mastercard 5555 5555 5555 4444, expiry 12/26, CVV 123 — authorises without 3DS.
3DS challenge: Visa 4022 0522 6704 0001, expiry 12/26, CVV 123 — triggers a 3DS redirect; complete the challenge on PayPlug's page.

Verify that:

The payment appears in your PayPlug/Dalenys back office.
The payment status updates correctly in Payrails.

Once verified in test mode, repeat the setup in live mode.

→ Continue to: Test a payment