MoneyPay Virtual POS describes card collection and stored-card use through Masterpass. Review the first card-entry journey separately from repeat purchases, and keep the cart, final payment result and customer request linked to the same order.
Compare first purchases with stored-card checkout
MoneyPay relates card storage to Masterpass. Selecting a stored card and completing an order payment are different steps. Focus order tracking on the final transaction result, and include both first-time and repeat-purchase examples in the account-specific review.
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 MoneyPay Virtual POS page describes 3DS verification. Official source | Not yet confirmed |
| Installments | Subject to merchant terms Installment sales depend on the card, bank and merchant scope. Official source | Not yet confirmed |
| Refund | Confirm the scope with us Determine the refund-service and user-permission scope separately. | Not yet confirmed |
| Partial refund | Confirm the scope with us Technical confirmation is required for partial refunds. | Not yet confirmed |
| Card storage | In provider documentation The provider describes card storage through Masterpass. Official source | Not yet confirmed |
| Currency | Confirm the scope with us Foreign-card acceptance alone does not establish foreign-currency collection. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Confirm preauthorization and later capture separately. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the MoneyPay 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 MoneyPay records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Does selecting a stored card complete the payment?
No. Card selection and the final payment result are different steps. Match the completed transaction to its order and test first-time and repeat purchases separately.
Can the review start with an existing MoneyPay 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.