Elekse presents Virtual POS, EsnekLink and marketplace solutions under the EsnekPos brand. Review whether the customer checks out in a store or follows a remote payment invitation, using the product enabled on the existing merchant account.
Match store sales and payment invitations to orders
EsnekLink describes sharing a payment link through social media, email or SMS, while web checkout starts from a cart. In both journeys, identify the reference that links collection to the order. Sales and finance should use the same sale record when reviewing the customer's payment status.
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 EsnekPos product. | Not yet confirmed |
| Installments | Subject to merchant terms Virtual POS installments are advertised; card and merchant scope govern use. Official source | Not yet confirmed |
| Refund | Confirm the scope with us Determine the refund-service scope enabled for the account. | Not yet confirmed |
| Partial refund | Confirm the scope with us Current technical confirmation is required for partial refunds. | Not yet confirmed |
| Card storage | Confirm the scope with us Review card storage for the selected product separately. | Not yet confirmed |
| Currency | Confirm the scope with us Clarify accepted payment currencies for the account. | Not yet confirmed |
| Preauthorization | Confirm the scope with us Confirm preauthorization and conversion to a sale separately. | Not yet confirmed |
Plan your MagicPay connection in three steps
Review the Elekse 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 Elekse records. Keep order references, completed payments, pending authorizations where applicable and confirmed refund results distinct.
Frequently asked questions
How should payment-link sales be matched to store orders?
Keep an order reference with the invitation and the resulting payment. The starting channel differs, but customer service and finance still need to identify the same sale.
Can the review start with an existing Elekse 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.