Ziraat Bankasi lists e-commerce Virtual POS separately from desktop and mobile POS, referring merchants to Bankkart POS for more detail. Review the internet-sales store in the existing agreement rather than reusing physical-terminal details.
Match physical and online sales to the correct account
Record the identifiers for the physical checkout and online store separately. Link each e-commerce order to its Virtual POS reference, channel, amount and result. This helps finance investigate a sale without confusing an in-store payment with an online collection.
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 3DS in the Virtual POS technical documentation. | Not yet confirmed |
| Installments | Confirm the scope with us Check installment configuration for the online store. | Not yet confirmed |
| Refund | Confirm the scope with us Clarify the Virtual POS refund flow and access permission. | Not yet confirmed |
| Partial refund | Confirm the scope with us The product list does not establish partial-refund support. | Not yet confirmed |
| Card storage | Confirm the scope with us Confirm card-storage scope with the bank. | Not yet confirmed |
| Currency | Subject to merchant terms Currencies depend on the online store's account scope. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Preauthorization is not documented in the reviewed Virtual POS description. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Ziraat 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 Ziraat Bankası records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Where should a business with physical POS start?
Identify the internet-sales channel and Virtual POS store in the merchant agreement. Keep physical-terminal information separate from e-commerce connection details.
Can the review start with an existing Ziraat 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.