Halkbank presents Virtual POS for online single-payment and installment sales. Its Web POS description covers a different collection journey based on customer instructions. Identify the collection channel in the existing merchant agreement before planning a MagicPay review.
Link customer-initiated payments to the order
Follow the online customer journey from product selection through order creation, installment choice and payment result. Record staff-operated collection separately with its own channel information. Halkbank describes Virtual POS and Web POS separately, so permissions and tests must follow the selected product.
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 3DS against the integration document supplied to the merchant. | Not yet confirmed |
| Installments | Subject to merchant terms The Virtual POS page advertises installments; account options need separate confirmation. Official source | Not yet confirmed |
| Refund | Confirm the scope with us Verify the technical refund channel and permission. | Not yet confirmed |
| Partial refund | Confirm the scope with us Confirm partial refunds for Virtual POS. | Not yet confirmed |
| Card storage | Confirm the scope with us The official product introduction does not describe the card-storage connection. | Not yet confirmed |
| Currency | Subject to merchant terms The payment currency depends on merchant account configuration. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Check preauthorization availability separately. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Halkbank 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 Halkbank records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Why distinguish Virtual POS from Web POS?
They describe different ways to initiate collection. Define whether the customer checks out online or staff act on an instruction, then match the agreement and tests to that channel.
Can the review start with an existing Halkbank 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.