QNBpay presents Virtual POS, Link POS and Digital POS for different payment starting points. Review the current agreement and separate an online basket from a remotely sent collection request before defining the MagicPay connection scope.
Separate the sale date from the settlement schedule
The merchant-panel information distinguishes payment activity from the settlement schedule. A successful sale date and a transfer date are not the same. Review the order result, refund activity and expected transfer separately so that customer transactions are not confused with cash-flow tracking.
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 integration guide describes a 3D payment service. Official source | Not yet confirmed |
| Installments | Subject to merchant terms Installments depend on participating card programs and merchant scope. Official source | Not yet confirmed |
| Refund | In provider documentation The merchant panel describes cancellation and refunds. Official source | Not yet confirmed |
| Partial refund | Confirm the scope with us Clarify API partial-refund and repeat-operation scope separately. | Not yet confirmed |
| Card storage | In provider documentation Card storage is explicitly listed among provider products. Official source | Not yet confirmed |
| Currency | Confirm the scope with us Verify foreign-card permission separately from collection currency. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Determine account permissions for preauthorization and capture. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the QNBpay 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 QNBpay records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Does the sale date establish the transfer date?
No. Payment activity and the settlement schedule are separate information. Keep the successful order result, refund movements and expected transfer distinct in finance review.
Can the review start with an existing QNBpay 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.