Pay N Kolay's integration guide distinguishes the customer return page from technical verification of the payment result. Review the existing Virtual POS account with attention to interrupted sessions, cancellations and refund references.
Track the result independently of the customer return
The official guide advises against treating a successful return page alone as proof of payment. Check the existing transaction reference before asking a customer to pay again after closing the browser or losing connectivity. Keep pending payments separate from confirmed final results.
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 integration guide describes 3DS payments and result checks. Official source | Not yet confirmed |
| Installments | Subject to merchant terms Installments depend on the card program, sector and agreement. Official source | Not yet confirmed |
| Refund | In provider documentation Cancellation and refunds are described according to panel and service rules. Official source | Not yet confirmed |
| Partial refund | Confirm the scope with us Confirm technical partial-refund scope separately. | Not yet confirmed |
| Card storage | Subject to merchant terms Card-storage infrastructure is defined within the commercial agreement. Official source | Not yet confirmed |
| Currency | Subject to merchant terms Currency choices depend on permissions configured on the account. Official source | Not yet confirmed |
| Preauthorization | Confirm the scope with us Clarify preauthorization and capture separately. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Pay N Kolay 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 Pay N Kolay records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Should an interrupted browser session trigger a second payment?
Not without checking the existing transaction. The provider guide distinguishes the return page from confirmed payment evidence, so inspect the current reference and result first.
Can the review start with an existing Pay N Kolay 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.