Turkiye Is Bankasi describes sales, installments, preauthorization and capture on its Virtual POS product page. Separate direct sales from reservation flows in which the final amount is determined later when preparing the MagicPay scope review.
Separate preauthorization from completed collection
Treat the reservation and final capture as different stages. Retain the first reference with the final sale so that finance and customer service can distinguish reserved funds from completed collection. Compare the order currency and amount with the merchant's permissions rather than assuming every listed currency is enabled.
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 requires 3D Secure for online Bankamatik-card transactions. Official source | Not yet confirmed |
| Installments | Subject to merchant terms Installment sales are advertised; match options to merchant scope. Official source | Not yet confirmed |
| Refund | Confirm the scope with us Verify the refund flow in current technical documentation. | Not yet confirmed |
| Partial refund | Confirm the scope with us Confirm partial refunds separately. | Not yet confirmed |
| Card storage | Confirm the scope with us Card storage is not documented in the reviewed product description. | Not yet confirmed |
| Currency | Subject to merchant terms Currencies including USD, EUR and GBP are listed for foreign cards; account permission governs use. Official source | Not yet confirmed |
| Preauthorization | In provider documentation The product page explicitly describes preauthorization and capture. Official source | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Türkiye İş Bankası 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 Türkiye İş Bankası records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
What matters when testing a Bankamatik card?
The bank specifies 3D Secure for online transactions with these cards. Check the authentication return and the final sale result as separate outcomes.
Can the review start with an existing Türkiye İş Bankası 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.