Payments
Payment is the step following checkout. When a user confirms checkout, he simultaneously creates a new order, and initiates a payment job. The user is redirected to the UI of the payment service provider to complete payment. Upon completion both the frontend and backend are updated of the status via a webhook.
Payment options
| β Pay.nl | ποΈ Mollie | ποΈ Ingenico | |
|---|---|---|---|
| iDeal | β | ||
| MasterCard | β | ||
| VISA | β | ||
| Apple Pay | β | ||
| Visa Mastercard | β | ||
| Google Wallet | β | ||
| Sofortbanking | β | ||
| Bancontact | β | ||
| Giropay | β | ||
| EPS | β | ||
| Multibanco | β | ||
| Bilk | β | ||
| Pay by Bank | β | ||
| Payconiq | β | ||
| Wechat Pay | β | ||
| Przelewy24 | β | ||
| Alipay Plus | β | ||
| PostePay | β | ||
| Carte Bancaire | β | ||
| Maestro | β | ||
| Americon Express | β | ||
| DanKort | β | ||
| Nexi | β |
Design decisions
- Payment job is initiated by the front-end stack upon clicking βconfirm orderβ
- Payment status is retrieved via webhook URL from front-end and a separate webhook URL from back-end, both configured in PSP