Ziraat Katilim describes Virtual POS for credit- and debit-card payments, reporting and payments from abroad. Review the existing online merchant store and treat the card's country, order currency and collection account as separate pieces of information.
Do not equate overseas cards with foreign-currency collection
The product description's reference to payments from abroad does not specify the transaction currency by itself. Compare the price shown to the customer, the amount sent to the bank and the collection account. Keep card origin and transaction currency separate in operational records.
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 the 3DS model against technical scope. | Not yet confirmed |
| Installments | Confirm the scope with us Clarify card and installment options for the store. | Not yet confirmed |
| Refund | Confirm the scope with us Confirm refund permission and connection method with the bank. | Not yet confirmed |
| Partial refund | Confirm the scope with us An explicit technical transaction definition is required for partial refunds. | Not yet confirmed |
| Card storage | Confirm the scope with us The Virtual POS page does not mention card storage. | Not yet confirmed |
| Currency | Subject to merchant terms Overseas payments are described; currencies depend on account scope. Official source | Not yet confirmed |
| Preauthorization | Confirm the scope with us Confirm preauthorization in current bank documentation. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Ziraat Katılım 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 Katılım records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Does an overseas card automatically mean foreign-currency collection?
No. Check the currency displayed to the customer against the transaction currency and account permission. The card's country alone does not establish foreign-currency collection.
Can the review start with an existing Ziraat Katılım 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.