Ziraat Pay describes multi-bank card acceptance and installment sales. For the existing merchant account, distinguish cancellation from refunds by considering the payment date, end-of-day processing and provider reference during the MagicPay scope review.
Separate cancellation and refund by end-of-day status
The provider describes cancellation for a transaction not yet included in end-of-day processing, and refunds for an approved transaction already processed. The same customer request can require different steps depending on timing. Keep the order number, payment date and provider reference together.
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 official API v2 documentation includes a 3D payment flow. Official source | Not yet confirmed |
| Installments | Subject to merchant terms Installment sales depend on eligible cards and merchant scope. Official source | Not yet confirmed |
| Refund | In provider documentation The provider describes portal refunds for approved transactions. Official source | Not yet confirmed |
| Partial refund | Confirm the scope with us Confirm partial amounts and repeated-refund conditions separately. | Not yet confirmed |
| Card storage | Confirm the scope with us Determine the card-storage scope enabled for the account. | Not yet confirmed |
| Currency | Confirm the scope with us Match payment and settlement currencies to the agreement. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Verify preauthorization and capture conditions separately. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Ziraat Pay 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 Pay records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Why does end-of-day status matter for a return request?
Ziraat Pay describes cancellation before end-of-day processing and refunds afterward for approved transactions. Check the original transaction and its timing before choosing the operation.
Can the review start with an existing Ziraat Pay 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.