Sipay Virtual POS describes card collection, installment choices and card storage. Review first-time and returning-customer checkout separately for the existing merchant account and match each order to its final payment result.
Review new-customer and repeat-purchase journeys
The card-storage description focuses on repeat shopping without re-entering card details. First-entry verification and later stored-card selection create different customer journeys. Review them separately while retaining an individual amount and final transaction result for every order.
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 The Sipay Virtual POS page describes 3D Secure. Official source | Not yet confirmed |
| Installments | Subject to merchant terms Single payments and installments are offered; card and account scope govern use. Official source | Not yet confirmed |
| Refund | Confirm the scope with us Confirm the refund channel and authorization scope. | Not yet confirmed |
| Partial refund | Confirm the scope with us Verify partial refunds against current technical documentation. | Not yet confirmed |
| Card storage | In provider documentation Card storage for repeat purchases is explicitly advertised. Official source | Not yet confirmed |
| Currency | Confirm the scope with us Clarify collection currencies for the existing merchant account. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Determine preauthorization and capture scope separately. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Sipay 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 Sipay records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Why test first-time and returning customers separately?
Initial card entry and later stored-card selection are different journeys. Both still require a confirmed final payment result linked to the individual order.
Can the review start with an existing Sipay 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.