HalkOde distinguishes preauthorization from direct sales. Review when an existing merchant account should authorize a payment and when collection should complete, particularly for stock checks, delivery preparation or services completed later.
Follow preauthorization through payment completion
The developer FAQ describes completing payment after preauthorization. Keep those stages separate in the order process. The FAQ also describes an authorized user's approval role for refunds; include the responsible person, transaction result and order reference in the operational 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 developer portal describes the 3D payment and verification flow. Official source | Not yet confirmed |
| Installments | Subject to merchant terms Services return installment information; card and account scope govern use. Official source | Not yet confirmed |
| Refund | In provider documentation The refund process describes approval by an authorized user. Official source | Not yet confirmed |
| Partial refund | Confirm the scope with us Confirm partial amounts and repeat-refund conditions separately. | Not yet confirmed |
| Card storage | Not offered in this scope The official FAQ explicitly says card storage is not yet offered. Official source | Not yet confirmed |
| Currency | Confirm the scope with us Clarify currency scope for the current merchant account. | Not yet confirmed |
| Preauthorization | In provider documentation Preauthorization and later payment completion are documented. Official source | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the HalkÖde 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 HalkÖde records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Is card storage confirmed in the provider source?
No. The cited HalkOde FAQ explicitly says it is not yet offered. This provider limitation must remain separate from the independently confirmed MagicPay support field.
Can the review start with an existing HalkÖde 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.