NomuPay presents hosted and merchant-owned payment pages as different integration models. Review where the customer enters payment details and returns after checkout, then link each order to its payment and refund references.
Retain refund references for multi-item carts
The support services describe full and partial refunds using an order number or MPAY reference. If only selected items are returned, relate the refund amount to the original sale. Keep the initial collection, refunded amount and remaining amount together so operations can follow the customer request.
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 3DS is documented for hosted and merchant payment pages. Official source | Not yet confirmed |
| Installments | Subject to merchant terms Single-payment and installment options depend on the card and account. Official source | Not yet confirmed |
| Refund | In provider documentation A full-refund service using the order or MPAY reference is described. Official source | Not yet confirmed |
| Partial refund | In provider documentation The refund service explicitly includes a partial-amount option. Official source | Not yet confirmed |
| Card storage | In provider documentation The provider technical document includes POS card storage. Official source | Not yet confirmed |
| Currency | Subject to merchant terms TRY, USD, EUR, GBP and RUB are documented; account scope governs availability. Official source | Not yet confirmed |
| Preauthorization | Confirm the scope with us Confirm preauthorization for the selected product. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the NomuPay 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 NomuPay records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
Which reference is useful for a partial return?
Keep the order number or MPAY payment reference with the returned items and refund amount. Compare the result with the original collection and remaining amount.
Can the review start with an existing NomuPay 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.