Lemonway Payment Page

1. Overview

The Lemonway Payment Page is a Lemonway fully hosted card payment solution enabling partners to accept payments without handling sensitive card data.

It is based on a redirection model, where the end-user is redirected to a secure Lemonway environment to complete a payment.

This approach allows Lemonway to manage:

PCI-DSS compliance
PSD2 / 3DS2 authentication
Secure card data processing
Payment routing

As part of the current rollout, this feature is being progressively activated per partner and represents the first step toward Lemonway’s new payment architecture.

Important: Existing card payment flows remain unchanged.

2. Key Capabilities

Hosted & Secure

Fully managed payment page with PCI-DSS, PSD2 and GDPR compliance handled by Lemonway.

Minimal Integration

Simple redirect-based implementation with no handling of sensitive card data.

Multiple Payment Flows

Supports one-shot payments, card registration, and one-click payments.

Customisable

Branding can be configured to align with your platform (logo and colors).

Multilingual

Supports EN, FR, ES, DE, IT with automatic fallback logic.

3. Payment Flow (Redirection Model)

flowchart LR
    A[User clicks "Proceed to Payment"] --> B[Redirect to Lemonway Payment Page]
    B --> C[User enters card details]
    C --> D[3DS2 Authentication (if required)]
    D --> E[Payment Processing]
    E --> F{Result}
    F -->|Success| G[Redirect to Merchant - Success URL]
    F -->|Failure| H[Redirect to Merchant - Failure URL]

4. Integration

Redirection URL

Token Generation

Use the MoneyInWebInit API:

Retrieve MONEYINWEB.TOKEN
- Inject into the redirection URL

5. Payment Flows

One-Time Payment

Standard card payment flow.

"registerCard": true | false

Optional card saving via checkbox.

One-Click Payment

Fast checkout using a previously saved card.

{
  "cardID": "...",
  "registerCard": false
}

Only CVV required. Full card details are not re-entered.

6. Sandbox Validation (Recommended)

To ensure correct behaviour for saved card payments:

Step 1 — Register a Card

Execute a payment with:
- Retrieve cardId
  - Confirm via GetCard
    
    Step 2 — Test One-Click Payment

Call:
With:
- cardId
  - "registerCard": false
    - Validate full redirect flow
      This ensures correct support for stored card payments.
    7. Branding (Optional)

Branding is configured via the Lemonway Dashboard. https://documentation.lemonway.com/docs/branding-lemonway-products-in-the-dashboard

Capabilities

Logo

Displayed on the Payment Page (top-left).

Formats: SVG (recommended), PNG, JPG
Types: Horizontal and Square

Colors

Primary color applied to key UI elements (e.g. Pay button).

HEX / RGB input
Live preview available

Permissions

Required: Edit Branding

Default roles:

MB-ADMIN
- MB-MANAGER
  - MB-OPERATOR

8. Language Handling

Supported ISO2 codes:

Behaviour

Uses lang parameter if provided
- Falls back to browser preferences
  - Defaults to English if unsupported
    Users can also switch language directly on the Payment Page.

9. Behaviour Rules

Default Lemonway branding applies if no configuration is set
- Branding is applied globally across supported products
  - Accessibility compliance must be ensured by the partner

10. Summary

The Lemonway Payment Page provides a secure, compliant, and low-integration payment solution built on a redirection model.

It allows partners to:

Avoid handling sensitive payment data
- Enable advanced payment flows (card registration and one-click)
  - Maintain brand consistency
    - Deliver a secure and trusted payment experience

If you want to push this further, the next logical step would be:

A second diagram showing token lifecycle + API interaction (this would elevate it to your reconciliation/KYC level of quality)