How Card Payments Work
Lemonway provides its Partners with a complete solution for processing card payments.
At Lemonway, we offer several card payment options; you can find them here.
Card payments work in four key steps:
- Once the basket is confirmed, your customer clicks the payment button on your website or application.
- A card transaction with the status Pending is created in your Dashboard (Type = Incoming / Method = Card / Status = Pending).
- The payment page opens, where your customer enters their card details (network, number, expiry date, and CVC) and completes the payment.
- The transaction is updated with card information (first four and last two digits, issuing country, etc.). Its status changes and Lemonway deducts its fee.
Accepted card networks and supported currencies
| Network | Card type | Geographic area | Accepted currencies |
|---|---|---|---|
| CB (Carte Bancaire) | Debit and Credit | France | EUR |
| Visa | Debit and Credit | International | EUR, GBP, CHF |
| Mastercard | Debit and Credit | International | EUR, GBP, CHF |
Activation of some networks may depend on your contract and geographic area. Contact your Account Manager to find out which networks are available in your configuration.
Pay In and Pay Out transactions are always processed in the currency of your Lemonway payment environment. Exchange rates are provided by the card-issuing bank. Other currencies may be activated on request, depending on your volumes.
Available Features and Card Registration
Depending on your contractual configuration, the following features are available:
| Feature | Description |
|---|---|
| One-shot payment | Single transaction without saving the card |
| One-click payment | Payment using a saved (tokenised) card, initiated by the customer without re-entering their details |
| Card pre-authorisation | Holds an amount on the card (for a deposit or when the final amount is unknown) for up to 6 days |
| Recurring payments (MIT) | Merchant-initiated transactions, such as subscriptions, recurring debits and deferred billing |
| Delayed capture | The actual debit takes place after the authorisation phase |
| Partial or full refund | Refund to the original card, through the Dashboard or API |
One-click and MIT features use secure card tokenisation. Lemonway stores card details in accordance with PCI DSS standards and returns a unique identifier (card_id) during the first payment with card registration. This identifier is used for subsequent transactions, so the customer does not need to enter their details again.
Recurring payments (MIT) are subject to specific regulatory requirements, including initial consent and informing the cardholder. Make sure your integration meets these obligations before activation.
Transaction statuses
| Status | Description |
|---|---|
| Success | The transaction has completed, and the amount is credited to the beneficiary's payment account. |
| Pending | The amount has not yet been credited, but the status may change to Success or Error. |
| Cancelled | The amount has not been credited. The customer did not complete the payment (for example, they closed the browser, did not enter the 3DS code, or the session timed out). |
Test Cards (Sandbox Environment)
In the sandbox environment, use the card numbers below to simulate different payment behaviours. For all test cards, use:
- Expiry date: any future date (for example,
12/26). - CVC: any three-digit code (for example,
123).
These test cards are valid only in the sandbox environment and when you are using Lemonway's new card structure. Using a test card in production results in an automatic decline (card.test).
For more information, contact your Account Manager or Lemonway Support.
Successful Payments
| Card number | Network | Behaviour |
|---|---|---|
4242 4242 4242 4242 | Visa | Successful payment |
5555 5555 5555 4444 | Mastercard | Successful payment |
Successful Payments by Issuing Country
| Card number | Country | Network |
|---|---|---|
4977 8300 0000 0001 | France | Visa |
4360 0000 0100 0005 | France | Visa / Carte Bancaire (CB) |
5130 2900 0000 0009 | France | Mastercard / Carte Bancaire (CB) |
4658 5800 0000 0008 | United Kingdom | Visa |
4023 6000 0000 0002 | Italy | Visa |
4571 7300 0000 0003 | Denmark | Visa |
4338 3000 0000 0009 | Argentina | Visa |
4835 9100 0000 0003 | China | Visa |
Specific 3D Secure Behaviours
| Card number | 3DS Behaviour |
|---|---|
4000 0000 0000 0101 | 3DS required and supported (challenge) |
4000 0000 0000 0119 | 3DS not supported by the card |
4000 0000 0000 3055 | 3DS v2 - frictionless flow (without fingerprint) |
4000 0000 0000 3063 | 3DS v2 - frictionless flow (with fingerprint) |
4000 0000 0000 3253 | 3DS v2 required for SCA; no authentication for MITs |
4000 0000 0000 0259 | 3DS v2 supported; v1 not supported |
4000 0000 0000 3238 | 3DS v2 not supported; v1 supported |
4000 0000 0000 3220 | 3DS v2 - fingerprint fails |
4000 0000 0000 3246 | 3DS v1 required, but v2 not supported |
Special Authorisation Behaviours
| Card number | Simulated Behaviour |
|---|---|
4000 0000 0000 0002 | Card declined |
4000 0000 0000 0010 | Authorisation succeeds, but every capture fails |
4000 0000 0000 2180 | Declined -card.do-not-honor |
4000 0000 0000 2198 | Declined - card.possible-fraud |
4000 0000 0000 2206 | Declined - card.no-money (insufficient funds) |
4000 0000 0000 2214 | Declined -card.expired |
4000 0000 0000 2222 | Declined - card.stolen (card reported stolen) |
4000 0000 0000 2230 | Declined - card.failed-cvc (invalid CVC) |
4000 0000 0000 2248 | Declined - card.failed-avs |
4000 0000 0000 2255 | Declined - card.not-authorized |
4000 0000 0000 2263 | Declined - card.inactive |
4000 0000 0000 2271 | Declined - card.lost |
4000 0000 0000 2289 | Declined - card.region-not-authorized |
4127 9694 2058 7632 | Declined - card.blacklisted |
Other Special Behaviours
| Card number | Simulated Behaviour |
|---|---|
4000 0000 0000 0028 | CVC verification fails |
4000 0000 0000 1216 | Verification succeeds, but every transaction fails |
4000 0000 0000 0069 | Payment succeeds, but a chargeback is initiated immediately |
4000 0000 0000 0200 | Payment succeeds, but a failed chargeback is initiated immediately |
4000 0000 0000 0309 | Payment succeeds, but a retrieval request is initiated immediately |
4000 0000 0000 0077 | Payment succeeds, but every refund is declined |
4000 0000 0000 4004 | Payment succeeds, but a fraud notification is sent |
4000 0000 0000 6223 | Payment succeeds, but every incremental capture fails |
4000 0000 0000 0531 | Authorisation succeeds, but every incremental authorisation fails |
4000 0000 0000 3303 | Authorisation succeeds, but every incremental authorisation fails with card.no-money |
4000 0000 0000 6009 | Verification succeeds, but new authorisations fail with card.no-money |
4000 0000 0000 4301 | Verification succeeds, but new authorisations fail with card.expired |
5337 4800 0000 7168 | The transaction fails with recommendation code do-not-retry |