DenizBank describes a hosted payment page and the Inter-CPOS recurring-collection solution separately. A one-off checkout and periodic collection serve different needs. Identify the contracted product before reviewing the MagicPay connection scope.
Separate checkout payments from recurring collections
For a hosted checkout, follow the customer's return to the order. For Inter-CPOS recurring or bulk collections, retain the collection period and customer relationship. Give the technical and finance teams the same distinction so that a transaction can be matched either to an order or to the correct collection period.
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 DenizBank Virtual POS page describes 3D Secure. Official source | Not yet confirmed |
| Installments | Confirm the scope with us Confirm that Inter-CPOS installment information applies to the selected VPOS product. | Not yet confirmed |
| Refund | Confirm the scope with us Verify the Virtual POS refund route with the technical team. | Not yet confirmed |
| Partial refund | Confirm the scope with us Confirm partial refunds for the specific product. | Not yet confirmed |
| Card storage | Confirm the scope with us Card storage and reference usage require a separate scope review. | Not yet confirmed |
| Currency | Subject to merchant terms EUR, USD, GBP, RUB and JPY are listed for foreign cards; verify store permission. Official source | Not yet confirmed |
| Preauthorization | Confirm the scope with us Confirm preauthorization separately from sale authorization. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the DenizBank 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 DenizBank records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Can Inter-CPOS details be assumed to apply to every DenizBank Virtual POS account?
No. Identify the selected product and confirm its account permissions. A recurring-collection description does not establish the same scope for a one-off hosted checkout.
Can the review start with an existing DenizBank 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.