By Card
Our card payments are processed by 5 partners: Atos, Payxpert, Payzen, Monetico, or Computop.
Why not upgrade your viewing experience! An updated version of this article is on our new documentation portal 👉 here
Web PSP or Direct Card Payments Mode?
Lemonway offers API methods for two types of card payment modes. Web PSP and Direct Payments.
Web PSP Payments are used when the end-user buys a service or good on your website and then is redirected to the PSP (Payment Service Provider) payment page. The benefits of using this mode are:
PSPs are PCI-DSS certified
PSPs usually support multiple currencies
PSPs support multiple payment methods (debit and credit cards, mobile wallets, and more)
Neither Lemonway nor the Partner process the bank card owners' data when this mode is used.
Direct Mode Payments are used when Partners choose to process payments using their own payment page. This mode is usually preferred when Partners want to avoid their users being redirected to another URL outside their network.
Partners using this mode are obliged to maintain a high level of network security and be PCI-DSS certified.
This section outlines Lemonway’s current card payment solutions and how you can implement them on a use case basis.
PSD2 impact for Card Payments
The Payment Service Directive, commonly known as PSP2 requires SCA (Strong Customer Authentication) to be implemented as part of a set of new measures to combat fraud and increase security. All CIT (Customer Initiated Transactions) are required to go through the 3-D Secure v2 protocol.
What does this change for you in short term?
Lemonway wants to ensure that card payments are processed smoothly with no declines, we will outline some recommendations and best practices to help you during this transition period.
For Partners using the Web PSP payment mode:
For One Time payments: use the MoneyInWebInit method, whether the end-user’s card is registered or not. The card owner will be authenticated with 3-D Secure.
For Subscriptions with equal recurring amounts: for the initial subscription payment, use MoneyInWebInit and ensure that you set: registerCard=1, then use MoneyInWithCardID for all subsequent equal amounts payments.
For Payments Upon Delivery: use MoneyInWebInit to pre-authorize the amount you will charge upon delivery. Ensure that you set the delayedDays field between 1 to 6 days. Depending on if you want to guarantee the payment or not, use MoneyInValidate or MoneyInWithCardID to capture the funds (details on the table below).
For PCI-DSS Partners using Direct Payment mode (no PSP page):
For One Time payments: use the MoneyIn3DInit method, whether their card is registered or not. The card owner will be authenticated with 3-D Secure. After the end-user has authenticated, you should call MoneyIn3DAuthenticate to check the status of 3D Secure Authentication after receiving a callback from PSP. Finally, call MoneyIn3DConfirm to finalize the payment.
For Subscriptions with equal recurring amounts: for the initial subscription payment, use the MoneyIn3DInit and then MoneyIn3DAuthenticate and MoneyIn3DConfirm as explained below. Use MoneyInWithCardID for all subsequent payments.
Lemonway does not recommend you use the MoneyIn and RegisterCard method from January 2021. Instead, you should use MoneyIn3DInit and MoneyIn3DConfirm only.
Our Current Use Case Solutions
Payment Use Case | Web PSP Payment | Direct Payment PCI-DSS Compliant | 3-D Secure Authentication | Legacy (No longer recommended) | |
---|---|---|---|---|---|
One Time Payment A payment made by the client that is a one-off (not repeated) transaction. | Method: MoneyInWebInit |
| Yes | MoneyIn | |
Differed Payment with Payment Guarantee Only available for Atos and, Payzen | Pre-authorization (Preauth) A sum of money that is approved by the client and is captured to make a payment later. | Method: MoneyInWebInit Ensure that you set delayedDays between 1- 6 days. |
Ensure that you set isPreAuth=1 and delayedDays between 1- 6 days. | Yes | MoneyIn |
Capture This is when the funds move from the pending stage, ready for you receive the money. | After initiating a pre-authorization, funds will be blocked by the Issuing Bank for 6 days maximum.
| No | |||
Subscription | Initialization Initial transaction for a subscription can be for a predetermined or an undetermined length of time. | Method: MoneyInWebInit registerCard=1 |
Ensure that you set: registerCard=1 (available from April) | Yes | |
Recurring Payments Transactions that follow an undetermined subscription period. These transactions are of the same initial amount. | Method: MoneyInWithCardID | No | |||
Payment Upon Delivery Only available for Atos and, Payzen | Purchase Day | Method: MoneyInWebInit Ensure that you set delayedDays between 1- 6 days. |
Ensure that you set isPreAuth=1 and delayedDays between 1- 6 days. | Yes | |
Charge Day |
| No |
- MoneyInWebInit: Initiate a Web Payment
- MoneyIn3DInit: Initiate a Direct Payment (PCI-DSS compliant only)
- MoneyInGetCard
- MoneyIn3DConfirm: Finalize a Direct Payment (PCI-DSS compliant only)
- MoneyIn3DAuthenticate: Check Money-In 3DS Status (PCI-DSS compliant only)
- (Deprecated) RegisterCard: Register a Card for Direct Payments (PCI-DSS compliant only)
- UnregisterCard: Delete a Card Token
- MoneyInWithCardId: Charge a Registered Card
- MoneyInValidate: Capture a Deferred Payment
- MoneyInSubscriptionInit : Initiate Monthly Recurring Payments