Vakif Katilim describes sending an online card-payment request to the bank and receiving an authorization result. Start the MagicPay review with the existing merchant agreement and store details, then connect the bank result to the order record.
Match store access to team responsibilities
Identify the employee using the panel separately from the technical owner of server-side credentials. Store identifiers can appear in working notes; secrets should remain in secure server configuration. Finance should work from order numbers, transaction references and results rather than connection credentials.
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 flow against current bank documents. | Not yet confirmed |
| Installments | Confirm the scope with us Establish the store's installment scope explicitly. | Not yet confirmed |
| Refund | Confirm the scope with us Clarify how refunds can be used through the connection. | Not yet confirmed |
| Partial refund | Confirm the scope with us Confirm partial-amount refunds separately. | Not yet confirmed |
| Card storage | Confirm the scope with us Card storage is not documented in the reviewed Virtual POS introduction. | Not yet confirmed |
| Currency | Subject to merchant terms The transaction currency depends on the merchant account scope. | Not yet confirmed |
| Preauthorization | Confirm the scope with us A general authorization description does not prove separate preauthorization support. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Vakıf 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 Vakıf Katılım records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Which store information belongs in the initial review?
Identify the internet sales channel, merchant store and technical owner. Do not put secret connection credentials in content or support forms.
Can the review start with an existing Vakıf 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.