1000pay presents Virtual POS and a digital wallet for different needs. For the MagicPay review, separate merchant collection from a customer's personal wallet use. Define the order reference, expected payment result and post-sale tracking for the existing account.
Distinguish Virtual POS needs from wallet usage
Identify the screen where payment begins and how the order reaches a final result. Name the merchant collection product explicitly. A sample order with its date, amount and reference gives technical and operational teams a concrete scope without treating wallet marketing as evidence of card-payment features.
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 The 3DS flow is not verified by a public technical source. | Not yet confirmed |
| Installments | Confirm the scope with us Confirm card and installment-term options for the merchant account. | Not yet confirmed |
| Refund | Confirm the scope with us Determine the refund channel, permission and transaction conditions. | Not yet confirmed |
| Partial refund | Confirm the scope with us Provider technical scope is required for partial refunds. | Not yet confirmed |
| Card storage | Confirm the scope with us A wallet product alone does not prove commercial card-storage support. | Not yet confirmed |
| Currency | Confirm the scope with us Clarify collection and settlement currencies separately. | 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 1000pay 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 1000pay records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Does the wallet description confirm merchant card storage?
No. Personal wallet features and commercial payment integration are separate scopes. Obtain product-specific technical confirmation for the merchant account.
Can the review start with an existing 1000pay 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.