The MagicPay catalog identifies Kuik with the kuikpara logo. Its wallet, card and money-transfer products serve different transaction needs. Begin the review with the exact product on the existing account rather than inferring merchant-payment capabilities from the brand.
Separate account movements from order collections
A wallet account can contain several types of movement. Preserve the order-collection reference separately and identify the product, transaction type and customer journey during the technical discussion. This lets operations distinguish a sale from other transfers or account activity.
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 the Kuik account's 3DS scope separately from other brands' products. | Not yet confirmed |
| Installments | Confirm the scope with us Clarify product and account scope for installments. | Not yet confirmed |
| Refund | Confirm the scope with us Determine the refund channel and permission during technical review. | Not yet confirmed |
| Partial refund | Confirm the scope with us Provider confirmation is required for partial refunds. | Not yet confirmed |
| Card storage | Confirm the scope with us The reviewed product page does not establish card-storage scope. | Not yet confirmed |
| Currency | Confirm the scope with us Check collection currencies for the merchant account. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Confirm preauthorization and capture separately. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Kuik 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 Kuik records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Which information should start a Kuik review?
Name the product in use, the transaction type and the expected customer journey. A wallet or money-transfer description alone does not establish merchant card-payment scope.
Can the review start with an existing Kuik 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.