Alternatif Bank describes online card collection, recurring collection and card storage on its Virtual POS product page. Prepare your existing merchant agreement for a MagicPay scope review by separating one-off purchases from recurring customer payments.
Connect the first payment with later collections
For stored-card requirements, review the first purchase, subsequent collections and removal of a card reference at the customer's request. Identify the service holding existing references without sharing card numbers. Keep each collection linked to its customer and order so that finance can reconcile the correct sale.
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 Confirm the 3DS model against the technical documentation supplied to the merchant. | Not yet confirmed |
| Installments | Confirm the scope with us Verify eligible cards and installment options separately. | Not yet confirmed |
| Refund | Confirm the scope with us Clarify the refund method and connection scope. | Not yet confirmed |
| Partial refund | Confirm the scope with us Technical confirmation is required for partial refunds. | Not yet confirmed |
| Card storage | In provider documentation The bank product page describes card storage. Official source | Not yet confirmed |
| Currency | Subject to merchant terms The transaction currency depends on the merchant account configuration. | 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 Alternatif Bank 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 Alternatif Bank records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
What helps when preparing stored-card payments?
Identify the service holding the existing card reference and its customer relationship, not the card number. Review collection frequency, customer consent and subsequent-payment requirements separately from the first sale.
Can the review start with an existing Alternatif Bank 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.