VakifBank publishes both an integration document and a management-panel guide for Virtual POS. Technical sale, refund and preauthorization flows should be reviewed alongside the panel's user roles when planning the MagicPay connection scope.
Separate inquiry permission from refund authority
Use the panel's administrator, user and inquiry roles to distinguish researching a sale from initiating a refund. For a partial return, retain the original amount, cumulative refunds and remaining amount. Keep the bank reference with the order and verify that total refunds do not exceed the original sale.
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 technical document describes a 3D Secure sale flow. Official source | Not yet confirmed |
| Installments | Subject to merchant terms Installment sales are documented; available choices depend on merchant configuration. Official source | Not yet confirmed |
| Refund | In provider documentation The technical document describes reference-based refunds. Official source | Not yet confirmed |
| Partial refund | In provider documentation Partial refunds below the sale amount are documented. Official source | Not yet confirmed |
| Card storage | Confirm the scope with us Card storage requires a separate product and connection review. | Not yet confirmed |
| Currency | Subject to merchant terms Currencies depend on the store's enabled account permissions. | Not yet confirmed |
| Preauthorization | In provider documentation The technical document defines preauthorization and capture. Official source | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the VakıfBank 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 VakıfBank records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Which amounts should partial-refund tracking retain?
Keep the original sale amount, total completed refunds and remaining amount together. The bank document states that cumulative refunds must not exceed the sale amount.
Can the review start with an existing VakıfBank 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.