Pratik Islem presents Virtual POS, payment links and QR collection for different customer starting points. Review the product enabled on the existing account and distinguish an online cart from a remotely received order before defining the MagicPay scope.
Match collection channels to transaction reports
The source of an order reference can differ between web checkout, a payment link and a QR flow. Retain the sales channel in the payment record and compare amount and date against the order. This gives sales and operations a common reference for daily review.
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 against current technical product scope. | Not yet confirmed |
| Installments | Subject to merchant terms Installment sales are advertised; card and account conditions govern availability. Official source | Not yet confirmed |
| Refund | Confirm the scope with us Determine refund permissions and transaction channel separately. | Not yet confirmed |
| Partial refund | Confirm the scope with us Technical confirmation is required for partial refunds. | Not yet confirmed |
| Card storage | Confirm the scope with us A digital-wallet introduction does not prove commercial card storage. | Not yet confirmed |
| Currency | Confirm the scope with us Clarify transaction and settlement currencies for the account. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Review preauthorization against the selected provider scope. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Pratik İşlem 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 Pratik İşlem records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Why keep the collection channel in reports?
A web cart, payment link and QR request can produce order references differently. The channel helps the team match a collection to the correct sale.
Can the review start with an existing Pratik İşlem 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.