Octet focuses on dealer and supplier collections as well as Virtual POS. When reviewing an existing account for MagicPay, define how debt, order and payment references relate to recurring commercial relationships.
Choose the right reference for dealer collections
A dealer code identifies the customer, an order number identifies a sale and a payment reference identifies the collection. Keep these separate when the same dealer has several open orders. Octet presents dealer-network collection and POS hosting for different needs; the selected product determines the scope to review.
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 Octet Virtual POS product describes 3D Secure. Official source | Not yet confirmed |
| Installments | Subject to merchant terms Installment collection depends on the card and merchant agreement. Official source | Not yet confirmed |
| Refund | Confirm the scope with us Clarify the refund method and account permission technically. | Not yet confirmed |
| Partial refund | Confirm the scope with us A split-payment service does not establish partial-refund support. | Not yet confirmed |
| Card storage | In provider documentation Octet describes card storage and repeat payments in its digital wallet. Official source | Not yet confirmed |
| Currency | Subject to merchant terms Foreign-currency collection depends on the export product and account scope. Official source | Not yet confirmed |
| Preauthorization | Confirm the scope with us Confirm preauthorization for the selected product. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Octet 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 Octet records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Are dealer codes and payment references interchangeable?
No. A dealer can have multiple orders and collections. Preserve the customer, order and payment identifiers separately to match each payment to the correct debt.
Can the review start with an existing Octet 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.