E-Commerce Integrations

Ready-made payment integrations for your online store.

Connect your store to MagicPay through a ready-made payment module or API. Manage installments, saved cards, routing and order-linked refunds in one flow.

Focus on your business with E-Commerce Integrations

A shared payment connection through ready-made modules and API
Installments, saved cards and automatic routing
Payment, cancellation and refund outcomes reflected in the store

Each new bank POS does not have to add a separate module and maintenance process to your store. MagicPay e-commerce payment integration connects your store to shared payment infrastructure through ready-made modules and API connections. Manage bank and provider accounts, installments and routing rules centrally. Your store retains its order lifecycle while payment outcomes, cancellations and refunds return with the same references. Your team does not rebuild payment logic for each new connection.

Start with a ready-made module or the API

Connect your existing checkout through a payment module installed from store administration. Teams building their own interfaces and order logic use the API route. Both approaches bring order references, amounts and provider outcomes into the shared model. A demo using your platform lets you see your store's actual payment step within that structure.

  • Module setup: establish the payment connection through store administration and MagicPay account settings.
  • API setup: combine your own checkout experience with the shared payment request.
  • Central management: manage supported bank connections and routing priorities from the MagicPay dashboard.

Payment features that work with the plugin

Installment options eligible for the card appear on the payment screen. Saved cards through MagicVault, provider selection through AI Routing and controlled retries for eligible technical errors stay connected to the same sale. Automatic POS removal and reactivation manage routes for new transactions according to connection health. Store teams follow these features' outcomes in the order and transaction history.

Send cancellations and refunds back to the store

A cancellation or refund initiated in the dashboard is matched to the original payment and order, and its outcome is reflected in the store's order status. Partial refunds retain the relationship between the amount and sale. Including coupons, shipping and promotions in testing keeps the customer-facing total aligned with the payment request. Finance and support work from the same record.

Who is it for?

Stores using ready-made e-commerce software, brands developing their own systems and sales teams centralizing multiple bank connections. To start a demo, share your platform, version, important checkout customizations and payment providers; you do not need to share passwords. We can then plan the transition around your actual order, delivery and refund processes.

Connect your store in three steps

Complete setup with after-sales checks, not just a single payment test.

  • 1. Choose a module or API starting point; match account connections and order statuses.
  • 2. Configure installments, saved cards and routing; test mobile payments and notification flows.
  • 3. Verify cancellations and partial refunds; track store and MagicPay records together after the transition.

Related solutions and resources

FAQ

Frequently asked questions about this product

Answers about usage, integration and operational scope.

How can I start setup? +

Connect your store through a ready-made payment module or the API. In a demo using your platform and existing checkout, we establish account, order and payment matching together.

Do I need to redevelop the store to add a bank? +

A new supported bank or provider account is added to the MagicPay connection layer. Your store continues using the shared payment model, and you manage routing priorities in the dashboard.

Are refunds reflected in my store order? +

Yes. Cancellation and refund outcomes connect to the store's order status through the original sale reference. Partial refund amounts are tracked in the same payment and order history.

What do we check during updates or migration? +

We run mobile checkout, authentication, payment notification, cancellation and partial refund scenarios. After the transition, we review existing bank modules to separate conflicting flows for the same sale.