ING's small-business guide discusses payment needs, application preparation and e-commerce infrastructure when choosing Virtual POS. Its POS product pages separately describe cash-register POS. Prepare an online-order example rather than treating a general guide as proof of account capabilities.
Apply the guide to the store payment journey
Show product selection, the cart total and the payment step in a short flow. Mark online sales as a separate channel if the business also uses a physical checkout. The technical and finance teams can then agree which bank result matches the sample order and which account documents are still needed.
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 Verify the ING account's 3DS model in product documentation. | Not yet confirmed |
| Installments | Confirm the scope with us A general guide does not document the merchant's enabled installments. | Not yet confirmed |
| Refund | Confirm the scope with us Confirm the refund channel and permissions separately. | Not yet confirmed |
| Partial refund | Confirm the scope with us Confirm account and connection scope for partial refunds. | Not yet confirmed |
| Card storage | Confirm the scope with us Provider-specific evidence is required for card storage. | Not yet confirmed |
| Currency | Subject to merchant terms The merchant account determines the currency used. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Review preauthorization as a separate requirement. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the ING 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 ING records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Are cash-register POS details sufficient for online sales?
No. Identify the merchant configuration for internet sales separately. Keep the contract and technical access for e-commerce distinct from physical-device setup.
Can the review start with an existing ING 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.