QNB's Virtual POS page discusses a live sales site or a test site available for review, including access to dealer-only websites. Prepare the journey leading to checkout as well as the payment screen when reviewing a MagicPay connection.
Prepare a dealer checkout for review
Use representative, non-customer data to show dealer login, product selection, order creation and payment. Keep review access limited and do not give reviewers payment secrets. Compare the amount displayed in the dealer order with the payment request, including any dealer-specific pricing.
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 QNB store's 3DS integration model. | Not yet confirmed |
| Installments | Confirm the scope with us Verify installment scope against merchant technical configuration. | Not yet confirmed |
| Refund | Confirm the scope with us Document the Virtual POS refund method separately. | Not yet confirmed |
| Partial refund | Confirm the scope with us Confirm the transaction conditions for partial refunds. | Not yet confirmed |
| Card storage | Confirm the scope with us The reviewed application page does not describe card storage. | Not yet confirmed |
| Currency | Subject to merchant terms Currency scope depends on account and product permissions. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Clarify preauthorization during the technical review. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the QNB 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 QNB records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
What belongs in a dealer review account?
Representative products and orders are sufficient. Restrict access to the journey under review; do not include real customer records or API secrets.
Can the review start with an existing QNB 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.