Our platform supports a wide range of payment methods to secure the best user experience for customers:
Cash
Terminal
Third-party payment systems (Partner operator and Operator API)
Credit/Debit Card
Apple pay
Corporate account
Customer Wallet
Consult the post Service configuration 3. Payment methods: types for details on payment methods set-up and payment flow.
Let us review the details of the mechanism that determines which payment method is selected for this or that order with order source = Customer app.
“Third-party payment systems” method is excluded from the mechanism as it is available exclusively for orders created via Operator app (Partner operator) or Operator API.
This leaves us with the following payment methods: Cash, Terminal, Credit/Debit Card, Apple Pay, Customer Wallet, Corporate account.
Payment methods priority for Customer app trips depends on several factors.
Primarily, for every order originated in the Customer app the system checks if Customer Wallet is enabled in Merchant and created in Customer app profile with positive balance.
1. In case Customer Wallet is
activated in merchant
created in Customer app profile
has a balance > 0
no other payment method is preset as a result of last manual selection
then the system chooses Customer Wallet as default payment method.
2. In case Customer Wallet is
NOT activated in merchant
Activated in Merchant, but NOT created in Customer app profile
has a balance ≤ 0
the following payment method selection rules apply:
Auto-selection (if the user has not manually selected a payment method yet)
Last manual selection (if the user has previously selected a payment method, for example “Cash”).
Credit/debit card (if added).
Apple pay (if available)
Cash. If card payment is available but the card is not added, cash payment is still chosen.
Terminal.
Corporate account.
If a customer previously preselected a specific payment method when he placed last order or browsed through services in the app, then the system remembers it and uses it in the future as a priod payment method.
Last manually selected payment method for a service is offered for the next order on this service and any service that has this payment method available.
If the last manually selected payment method is not available for this or that service the system offers the default payment method.
A customer can manually change payment method for each service before placing an order.
Example:
Wallet is set as the default payment method. The customer placed an order on Classic service manually selecting Card. The system set Card as last manual selection. After that the customer browsed through the app and manually selected Terminal for Business service. The system considers Terminal as a new manual selection. Terminal will be offered as the payment method for the next order on all the services that have it available.
NB Relogin (log out - sign in) erases the 'memory' of last manual selection
IMPORTANT
If there are services with different sets of payment methods within one service type (e.g. 2 Classic services) both auto-selection and last selection rules apply.
There are two major points here:
If a customer has chosen a card (whether it is an auto-selection or a saved choice), but there is one service in the service type that supports cards and another service that only supports cash, the system sends an order for the service that supports card payments. However, the user can always manually change the payment method.
If a customer has added a card, but the service type he needs only supports cash, then when choosing this service the system switches the payment method to cash. And if the user switches to another service type that supports cards, then the payment method should switch back to the card.
Read more on “Payment methods” sub tab in the Side menu for the Customer app in "Payment methods" in customer app.
