Lidio says its Virtual POS service can be used alongside POS agreements with other banks and payment institutions. Review the existing POS map and identify the account behind each sales channel before defining the MagicPay connection scope.
Review existing POS relationships together
Lidio presents Virtual POS, card storage and the merchant panel as separate product areas. List current POS contracts and distinguish first payments, repeat purchases and post-sale tracking. Use common order and payment references without assuming that every product is enabled on the same account.
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 Determine 3DS configuration for the selected Lidio product. | Not yet confirmed |
| Installments | Confirm the scope with us Clarify card programs and installment permissions for the existing account. | Not yet confirmed |
| Refund | Confirm the scope with us Confirm the refund service and merchant permission technically. | Not yet confirmed |
| Partial refund | Confirm the scope with us A split-payment product does not establish partial-refund support. | Not yet confirmed |
| Card storage | In provider documentation Lidio offers a separate card-storage product. Official source | Not yet confirmed |
| Currency | Subject to merchant terms Multiple-currency use depends on product and account scope. Official source | Not yet confirmed |
| Preauthorization | Confirm the scope with us Technical confirmation is required for preauthorization and capture. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Lidio 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 Lidio records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
What should be included in the existing POS map?
List current provider agreements, sales channels and enabled products. Separate first-payment, stored-card and post-sale needs before reviewing which connection handles each requirement.
Can the review start with an existing Lidio 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.