Checkout.com distinguishes reserving funds from completing collection. Review these stages against stock checks or delivery preparation in the existing account. Keep order, payment and refund references linked for the MagicPay scope discussion.
Distinguish authorized amounts from captured amounts
The provider describes payment states such as pending, authorized, captured and refunded. Retain those distinctions so that an uncaptured order is not treated as a completed collection. Use the original payment reference when reviewing a full or partial refund and its relationship to the 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 | In provider documentation Checkout.com Flow documentation describes 3DS authentication. Official source | Not yet confirmed |
| Installments | Confirm the scope with us These sources do not verify Turkish-card installments. | Not yet confirmed |
| Refund | In provider documentation Full refunds are documented for the provider dashboard and API. Official source | Not yet confirmed |
| Partial refund | In provider documentation Partial refunds of captured payments are documented. Official source | Not yet confirmed |
| Card storage | In provider documentation Saving payment details for subsequent payments is documented. Official source | Not yet confirmed |
| Currency | Subject to merchant terms The transaction currency depends on account and payment-method scope. Official source | Not yet confirmed |
| Preauthorization | In provider documentation Authorization and later capture are described as separate states. Official source | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Checkout 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 Checkout records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Is an authorized amount the same as collected funds?
No. Authorization and capture are separate states. Operations should identify the capture result before treating the order as a completed collection.
Can the review start with an existing Checkout 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.