Akbank describes 3D Secure, Axess and Wings installment sales, and full or partial refunds through its banking channels. Review your existing merchant agreement alongside the customer payment choice and the records your finance team will reconcile.
Match Axess and Wings choices to refund tracking
Prepare a cart using only the card and installment options enabled for your merchant account. Test a whole-order return separately from a single returned item. Akbank describes full and partial refunds in its mobile and internet channels; keep the original sale, refunded amount and remaining amount together. Confirm the MagicPay refund path independently.
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 product page describes 3D Secure verification. Official source | Not yet confirmed |
| Installments | Subject to merchant terms Axess and Wings installments depend on merchant configuration. Official source | Not yet confirmed |
| Refund | In provider documentation Full refunds through Akbank Mobile and Internet are described. Official source | Not yet confirmed |
| Partial refund | In provider documentation The bank channels describe refunding part of an order. Official source | Not yet confirmed |
| Card storage | In provider documentation The product description includes the bank's card-storage service. Official source | Not yet confirmed |
| Currency | Subject to merchant terms TRY, USD, GBP, EUR and JPY are listed; account permission is required. Official source | Not yet confirmed |
| Preauthorization | Confirm the scope with us Confirm preauthorization for the existing store. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Akbank 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 Akbank records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Does a refund in the bank panel prove MagicPay refund support?
No. The provider source documents the bank channel. Confirm the separate MagicPay flow using the sale reference, requested amount and final refund result.
Can the review start with an existing Akbank 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.