Anadolubank describes Virtual POS for online credit- and debit-card payments, including single payments, installments and 3D Secure. Turn this product information into an account-specific review using representative shopping carts.
Verify single-payment and installment carts separately
The bank describes both sale types, but the available installment count depends on the merchant configuration. Compare the card type, customer total and bank result for the same cart. Agree which report field carries the installment choice so that payment-screen behavior and financial review use the same reference.
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 bank describes 3D Secure for Virtual POS. Official source | Not yet confirmed |
| Installments | Subject to merchant terms Installment sales are advertised; confirm enabled options for the merchant. Official source | Not yet confirmed |
| Refund | Confirm the scope with us Confirm the Virtual POS refund method in technical documentation. | Not yet confirmed |
| Partial refund | Confirm the scope with us Obtain provider confirmation for partial refunds. | Not yet confirmed |
| Card storage | Confirm the scope with us Card storage is not documented in this product description. | Not yet confirmed |
| Currency | Subject to merchant terms The transaction currency depends on store and account configuration. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Clarify preauthorization and capture support separately. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Anadolubank 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 Anadolubank records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
How should installment tests be selected?
Use the installment options approved for the merchant, not every option mentioned in general product material. Compare the cart total, chosen installment count and final transaction result.
Can the review start with an existing Anadolubank 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.