Review an existing Papara merchant account by linking its payment identifier to the business order number. The payment-screen journey, result and later refund request should refer to the same order, with scope confirmed for the selected merchant product.
Distinguish the customer return from the payment notification
The return page completes the customer experience; the payment result supports operational tracking. Treat them as separate steps so that closing the browser does not lose the reference that operations must inspect. A later refund request should be linked to the same payment identifier.
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 3DS for the selected commercial payment method. | Not yet confirmed |
| Installments | Confirm the scope with us The reviewed document does not establish merchant installment scope. | Not yet confirmed |
| Refund | In provider documentation The official client describes refunds using the completed payment identifier. Official source | Not yet confirmed |
| Partial refund | Confirm the scope with us The documented refund example does not establish partial-amount support. | Not yet confirmed |
| Card storage | Confirm the scope with us Determine card-storage scope for the commercial integration separately. | Not yet confirmed |
| Currency | Confirm the scope with us Verify account-balance currencies separately from payment-acceptance scope. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Confirm preauthorization and later collection separately. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Papara 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 Papara records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Is the customer return page enough to confirm payment?
No. Match the order to its payment identifier and confirmed result. The return page and transaction notification have different roles, especially if the customer closes the browser.
Can the review start with an existing Papara 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.