Business and catalogue review
The merchant completes KYB and identifies the sites, apps, products or services it sells. Prohibited and restricted activities are reviewed before live processing, not after a checkout is embedded.
Ecommerce payments
Let customers pay their way. Keep every order connected.
Use hosted checkout, payment links or the payments API to accept the methods enabled for each transaction—including stablecoins, cards and mobile money where available—while preserving order references, signed status updates and finance reconciliation.
- Hosted checkout or API
- Stable order references
- Payment status and reconciliation
Fit and onboarding
A payment surface should fit the store, catalogue and fulfilment model.
ZyndPay supports approved businesses that need online collection and settlement. The onboarding review looks at the legal entity, beneficial owners, products, sales channels, fulfilment, refund model, countries and expected payment flows before live methods are enabled.
Customer and market context
Available methods depend on the customer, currency, country and enabled account configuration. Mobile money is one useful rail where it is the norm, not ZyndPay’s global identity or a universal promise.
Fulfilment and refund ownership
The merchant remains responsible for product quality, delivery, cancellation policy, customer service and lawful refund decisions. ZyndPay records and executes supported payment actions within the agreed service.
Integration artifact truth
Hosted checkout, payment links and the payments API are the public integration paths. This page does not advertise a WooCommerce, WordPress or cart plugin without a maintained public artifact.
Order-to-cash flow
Connect the cart, payment and finance record with one reference.
The merchant creates a payment for a real order, sends the buyer through an enabled payment path, waits for authoritative status, fulfils once its own policy is satisfied and reconciles every exception back to the same reference.
- 01
Create an immutable order reference
Generate a unique merchant reference and amount in the correct currency minor units. Keep prices, tax, delivery and inventory logic in the commerce system that owns the order.
- 02
Open checkout or share a payment link
Redirect to hosted checkout, create a payment link or use the supported API flow. The buyer sees the methods enabled for that account and transaction context.
- 03
Wait for confirmed server-side status
Use signed asynchronous events and authenticated status checks. Browser returns, screenshots and customer messages do not prove settlement and should not trigger fulfilment alone.
- 04
Fulfil and communicate clearly
Advance the order according to your own confirmed-payment policy. Keep pending, failed, expired, refunded and disputed states understandable to customer support.
- 05
Reconcile and settle
Match ZyndPay identifiers to orders, payment events, refunds and settlement records. Pricing, settlement timing and available withdrawal paths remain account-specific.
Commerce operations
Conversion matters. Traceability keeps the conversion useful.
Hosted, responsive checkout
Use a ZyndPay-hosted payment surface that adapts to mobile and desktop while your store retains catalogue, order and fulfilment ownership.
Payment links
Create a shareable payment path for invoices, remote sales or assisted checkout, with a merchant reference that returns to the same reconciliation model.
Payments API
Create and observe supported payment flows from your back end when you need a tighter connection to carts, subscriptions, order management or internal workflows.
Stablecoin acceptance
Accept enabled USDT or USDC asset-network pairs. The exact pair and address shown for the transaction must be used; blockchain finality and asset risk remain relevant.
Local payment rails
Present enabled card or mobile-money options where they are available, without hardcoding a provider or assuming the same methods exist in every market.
Refunds and reconciliation
Track supported refunds and exceptions separately from the original charge, then compare order state, payment state and settlement state with stable identifiers.
Operational truth
One payment ID should explain the order from attempt to settlement.
The buyer experience, your order system and finance records move at different speeds. A sound integration preserves the link among them without collapsing pending, confirmed, refunded and settled into one vague “paid” flag.
- Buyer evidence
- The return page tells the buyer what happened next. It does not replace the signed or authenticated server-side state used by the merchant.
- Finance evidence
- Payment status, refund status, settlement and withdrawal are related but distinct records. Reconcile them rather than deriving every answer from the storefront.
- Commercial evidence
- The applicable fee and terms are shown for the account and transaction before live processing. This page intentionally contains no universal rate table.
Choose a path
Launch quickly, then integrate as deeply as the store needs.
Hosted checkout
Send buyers to a responsive hosted surface and consume the confirmed result in your order system.
Explore hosted checkoutPayment links
Collect against an invoice or assisted-sale reference without building a complete custom checkout first.
Explore payment linksPayments API
Connect payment creation, status and events to a custom cart, order-management system or commerce backend.
Explore the payments APIFAQ
Ecommerce payment questions
Which payment methods can an online store accept?
An approved account may offer enabled stablecoin, card and mobile-money methods. The live checkout or API response is authoritative because availability varies by account, market, currency, customer context and rail status.
Does ZyndPay have a WooCommerce or WordPress plugin?
ZyndPay does not advertise a maintained public commerce plugin today. The verified integration paths are hosted checkout, payment links and the payments API. A plugin should be named only after its public artifact and maintenance path are verified.
Can I fulfil an order when the buyer returns to my site?
Do not use the return alone as payment proof. Confirm the authoritative server-side state and process signed events idempotently; the buyer may close the page early or a rail may still be pending.
Can ZyndPay settle every payment in stablecoins?
Settlement assets, timing and withdrawal paths depend on the approved account, original rail, enabled asset-network pairs and applicable terms. They are confirmed during onboarding and in the account surfaces, not guaranteed universally here.
How are refunds handled?
Supported refund requests remain separate transactions linked to the original payment. Eligibility, destination, finality and timing depend on the original method and rail; a blockchain transfer cannot always be reversed like a card payment.
Does ZyndPay publish ecommerce transaction fees?
No universal fee is published. Applicable pricing is account-specific and is disclosed in the dashboard, checkout, API responses or merchant terms before live processing.
Merchant onboarding
Let’s connect payments to your store.
Share the legal entity, storefront domains or apps, products sold, target markets, currencies, expected payment methods, refund model and technical owner. The team can then qualify the account and integration path without guessing at availability.