Checkout should show your customer exactly what to do to complete a purchase. Complicated fields, unclear error messages and an unfamiliar look make that decision harder. The MagicPay payment form connects a branded interface to your bank and payment institution connections. As customers choose a method and eligible installment plan, the order, authentication and payment outcome share one transaction reference. Your team can follow the sale without piecing its status together from separate screens.
Choose the payment model that fits your needs
Start with a ready-made payment page or embed payment fields in your existing shopping experience. Teams building their own interface use the same transaction model through the API. The presentation can change without breaking the link between payment and order.
- Hosted payment page: the customer is redirected to a payment page and returns to your store after the transaction.
- Embedded payment form: payment fields appear within your website with your brand's look and feel.
- API: your development team builds the interface while MagicPay provides the connection and transaction layer.
Your brand's voice, a comfortable mobile experience
Your logo, colors, typography and button labels are part of the payment experience. The amount, currency and eligible options are clearly visible. On mobile, the field order and clear guidance help customers know where they are when entering card details or returning from authentication. A pending outcome is explained differently from a completed sale.
Track transaction references instead of handling card data
With hosted pages and embedded fields, card details are sent directly to the payment infrastructure; your store tracks payments using a transaction reference. Saved cards through MagicVault, wallets, checkout financing and installment options join the form through your active connections. Finance and support teams follow the outcome in the order-linked record without copying card details into messages or operational notes.
Who is it for?
Online stores, digital services, membership platforms and brands selling within apps. Product teams retaining their design, developers centralizing payment connections and support teams needing a clear order status all benefit from the same flow. When adding a method, the customer interface and the post-sale record are considered together.
Launch your payment form in three steps
Bring the customer-facing screen into service alongside your actual order and refund workflows.
- 1. Choose a hosted page, embedded form or API model; connect your brand design and order reference.
- 2. Configure providers, installments and payment methods; test mobile and authentication scenarios.
- 3. Apply the payment outcome to the order; track pending transactions, cancellations and refunds from the same dashboard.