QPay describes collection using credit, debit and virtual cards, with installment choices presented during payment. Review representative carts from the existing merchant account and make the selected term and customer total clear.
Keep card type and installment choice with the cart
QPay describes displaying eligible installments after card information is entered. Retain the selected installment term and total in the original sale record. Customer service can then examine a payment question using both the cart and the collection record rather than an isolated amount.
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 | Confirm the scope with us Confirm the technical 3DS scope of the card-verification model. | Not yet confirmed |
| Installments | Subject to merchant terms Installment choices are advertised; terms depend on the card and merchant. Official source | Not yet confirmed |
| Refund | Confirm the scope with us Clarify refund account and transaction scope. | Not yet confirmed |
| Partial refund | Confirm the scope with us Confirm current technical scope for partial refunds. | Not yet confirmed |
| Card storage | Confirm the scope with us Verify commercial card storage independently of wallet features. | Not yet confirmed |
| Currency | Confirm the scope with us Foreign-card acceptance must not be interpreted as foreign-currency collection. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Review preauthorization against current merchant documentation. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the QPay 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 QPay records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
What should be retained from the installment choice?
Keep the selected term, total amount and order reference together. Use only card and installment options confirmed for the merchant account.
Can the review start with an existing QPay 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.