PayTR presents iFrame and Direct API as different payment experiences. Review the existing checkout and merchant account, retaining the order number as a key reference for payment and post-sale operations.
Track refund amounts using the order number
The refund service uses the order number and refund amount for full or partial returns. Preserve the original sale reference so it remains available later. For multi-item purchases, review the original amount, completed refunds and remaining amount together.
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 Direct API payment document includes a 3DS flow. Official source | Not yet confirmed |
| Installments | Subject to merchant terms Installment queries are documented; choices depend on the card and account. Official source | Not yet confirmed |
| Refund | In provider documentation The API describes full refunds using the order number. Official source | Not yet confirmed |
| Partial refund | In provider documentation The Refund API supports refunding part of the order amount. Official source | Not yet confirmed |
| Card storage | In provider documentation The Direct Card Storage API lists registration and payment services. Official source | Not yet confirmed |
| Currency | Confirm the scope with us Clarify the merchant's collection currencies for the account. | Not yet confirmed |
| Preauthorization | Confirm the scope with us A preauthorization heading exists; confirm the applicable technical scope separately. Official source | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the PayTR 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 PayTR records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
What is the key reference for a PayTR refund review?
Retain the original order number with the requested refund amount. Check the completed refund against the original collection and any previous refunds.
Can the review start with an existing PayTR 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.