PayInAll presents Virtual POS, mobile POS and physical POS as different payment journeys. Review the existing provider account by identifying the order and collection reference for each sales channel instead of assuming one product's scope applies to another.
Keep online and physical collections distinct
Retain whether a sale started at web checkout or on an in-store device. Include the installment choice and collection date with that record so that a customer request can be traced to the right order. Define acceptance tests for the selected product and confirm MagicPay support independently.
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 PayInAll describes 3D Secure for Virtual POS. Official source | Not yet confirmed |
| Installments | Subject to merchant terms Installment terms depend on bank agreements, card programs and sector scope. Official source | Not yet confirmed |
| Refund | Confirm the scope with us Clarify the refund channel and account permission. | Not yet confirmed |
| Partial refund | Confirm the scope with us Confirm current technical scope for partial refunds. | Not yet confirmed |
| Card storage | Confirm the scope with us Card storage is not documented in the reviewed official FAQ. | Not yet confirmed |
| Currency | Confirm the scope with us Determine currencies independently of card-acceptance scope. | 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 PayInAll 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 PayInAll records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Can physical POS permissions be assumed for Virtual POS?
No. The products describe different channels. Identify the online merchant account and confirm its technical scope separately from device-based payments.
Can the review start with an existing PayInAll 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.