Sekerbank requires 3D Secure in its Virtual POS application criteria. Its product page also covers the sales website, contact details, payment page and terms of sale. Prepare the MagicPay review around the complete customer journey, including interrupted authentication.
Make the 3DS requirement part of the order journey
Test successful verification as well as customers closing the authentication screen or returning to the order page. Link each attempt to its order. Operations should distinguish a completed sale from an unfinished payment before customer service suggests another attempt.
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 in its application criteria. Official source | Not yet confirmed |
| Installments | Confirm the scope with us Confirm Virtual POS installment scope for the merchant. | Not yet confirmed |
| Refund | Confirm the scope with us The product description does not detail the technical refund method. | Not yet confirmed |
| Partial refund | Confirm the scope with us Confirm partial refunds against technical documentation. | Not yet confirmed |
| Card storage | Confirm the scope with us Review the card-storage service and connection separately. | Not yet confirmed |
| Currency | Subject to merchant terms Accepted currencies depend on account permissions. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Obtain technical confirmation for preauthorization. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Şekerbank 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 Şekerbank records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Which authentication outcomes should be reviewed?
Include successful, abandoned and unresolved verification attempts. A return to the shop must be matched to the payment result rather than treated as proof of collection.
Can the review start with an existing Şekerbank 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.