TKPAY's business solution presents card collection, installment options and transaction reports. Review the existing merchant account by connecting the paid order with the records used by finance and customer service.
Read payment reports alongside refund records
The business product describes panel management of transactions, reports and refunds. Compare a sale amount with any later refund movement while preserving the transaction date and reference. This helps operations identify which sale a customer request concerns and lets finance inspect the same record.
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 technical 3DS model for the product. | Not yet confirmed |
| Installments | Subject to merchant terms Single payments and installments are advertised; card and account scope govern use. Official source | Not yet confirmed |
| Refund | In provider documentation The business product describes panel-based refund management. Official source | Not yet confirmed |
| Partial refund | Confirm the scope with us Separate technical confirmation is required for partial refunds. | Not yet confirmed |
| Card storage | Confirm the scope with us Determine merchant card-storage scope separately. | Not yet confirmed |
| Currency | Confirm the scope with us Clarify collection and settlement currencies for the 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 TKPAY 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 TKPAY records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
What should a daily payment review retain?
Keep each order's sale amount, transaction date, payment reference and any subsequent refund movement together. A customer request should remain traceable to its original sale.
Can the review start with an existing TKPAY 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.