Tosla Isim presents business Virtual POS and payment-link products separately from personal Tosla usage. Review the existing merchant account against both store carts and remote orders, identifying how each customer starts and completes payment.
Connect store carts and remote orders to collection
A store checkout usually obtains the order number from the cart, while a remote sale must associate it with the payment invitation. Match the sales team's order record to the payment record checked by finance. Keep commercial card-storage scope separate from consumer-wallet features.
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 for the existing Virtual POS account. | Not yet confirmed |
| Installments | Confirm the scope with us Clarify eligible cards and installment terms separately. | Not yet confirmed |
| Refund | Confirm the scope with us Determine the refund channel and account permission during technical review. | Not yet confirmed |
| Partial refund | Confirm the scope with us Current technical scope is required for partial refunds. | Not yet confirmed |
| Card storage | Confirm the scope with us Confirm commercial card storage independently of the personal wallet. | Not yet confirmed |
| Currency | Confirm the scope with us Clarify collection currencies for the merchant account. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Confirm preauthorization and capture separately. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Tosla İşim 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 Tosla İşim records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
How does a remote order retain its payment reference?
Associate the order record with the payment invitation before collection. Finance and customer service should be able to trace the resulting payment to that same sale.
Can the review start with an existing Tosla İşim 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.