Moka United presents Virtual POS, physical POS and payment links for different channels. Review card storage for returning customers separately from payment and refund records in the existing account before confirming the MagicPay connection scope.
Separate customer cards from payment records
The developer portal organizes customer, card and payment operations in separate service groups. A returning customer can make several purchases, each with its own transaction reference. Link a refund to the relevant sale, not merely to the customer's stored card.
Payment capabilities and integration scope
This table distinguishes published provider capabilities from merchant-specific conditions. A feature offered by a provider is not automatically enabled on every MagicPay connection.
| Capability | Scope and conditions | In MagicPay |
|---|---|---|
| 3D Secure | In provider documentation The official developer portal includes 3D Secure payment services. Official source | Not yet confirmed |
| Installments | Confirm the scope with us Clarify card programs and installment choices for the account. | Not yet confirmed |
| Refund | In provider documentation Payment cancellation and refund requests are documented as separate services. Official source | Not yet confirmed |
| Partial refund | Confirm the scope with us Confirm partial-refund conditions for the selected service. | Not yet confirmed |
| Card storage | In provider documentation Customer and card add, update and delete services are available. Official source | Not yet confirmed |
| Currency | Subject to merchant terms A Foreign Currency POS product is advertised; account product scope governs use. Official source | Not yet confirmed |
| Preauthorization | Confirm the scope with us Confirm account permissions for preauthorization and capture. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Moka United account
Identify the existing merchant agreement, sales channel, store configuration and enabled products. Confirm the required payment scenarios and the separate MagicPay connection scope before activation.
Test the approved configuration
Authorized technical staff should configure credentials through a secure server-side channel. Compare successful, rejected and interrupted payments, and test refund or stored-card scenarios only where their scope has been confirmed.
Reconcile orders and payment results
After acceptance, compare the enabled transaction flows with Moka United records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Why keep customer and payment references separate?
A customer or stored card can be used for multiple purchases. Each collection and later refund must still identify the specific sale and its transaction reference.
Can the review start with an existing Moka United account?
Yes. Start with the current merchant product and agreement. Account permissions, technical access and the independently confirmed MagicPay scope must be reviewed before deciding which flows can be activated.
Does provider documentation confirm that a feature is ready in MagicPay?
No. The provider notes describe its published scope and merchant conditions. The separate In MagicPay column remains Not yet confirmed until the technical connection scope is independently verified.