Paycell presents Virtual POS and payment links separately from mobile carrier billing. This review concerns merchant card collection on the existing account, with the order amount, installment choice and final result kept together.
Separate Virtual POS from carrier billing
The corporate product page lists Virtual POS, payment links and Faturana Yansit under different headings. Identify the selected payment product in operational records. Do not infer merchant card-storage or Virtual POS scope from the consumer application or mobile-billing product.
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 Virtual POS account's 3DS flow technically. | Not yet confirmed |
| Installments | Subject to merchant terms Installments depend on eligible business activities and participating card programs. Official source | Not yet confirmed |
| Refund | Confirm the scope with us Clarify the card-collection product's refund process. | Not yet confirmed |
| Partial refund | Confirm the scope with us Confirm partial-refund scope for the selected product. | Not yet confirmed |
| Card storage | Confirm the scope with us Card registration in the consumer app does not establish Virtual POS adapter scope. | Not yet confirmed |
| Currency | Confirm the scope with us The merchant account determines the collection currency. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Confirm preauthorization and capture scope separately. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Paycell 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 Paycell records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Should carrier billing be included in a Virtual POS test by default?
No. Paycell describes these as different products. Identify the merchant card-collection account and review mobile billing separately if it is required.
Can the review start with an existing Paycell 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.