Payment method coverage

Droplinked is a multi-PSP platform: checkout aggregates several providers behind one flow, and the provider that ends up taking the money depends on the shop, its region, and what that merchant has connected. This page states what is actually live. It is deliberately shorter than the list of providers with code in the platform, because a provider having an integration is not the same as a provider taking money.

Live today

These carry real money in production.

Provider	Method family	Renderer returned by the resolver
Stripe	Card	`STRIPE_ELEMENTS` (in-page Elements)
PayPal	Wallet	`PAYPAL_REDIRECT`
Paymob	Card, regional (MENA)	`PAYMOB_REDIRECT`
MamoPay	Card (GCC)	`MAMOPAY_HOSTED`

Integrated, not certified live

Code exists, and in some cases a health probe answers, but these are not carrying live merchant money today. Do not plan a launch around them, and do not present them to a merchant as available.

Provider	Status
Telr	Integrated. Not certified live.
Bonum	Integrated; health probe answers. Not certified live.
AzamPay	Integrated (mobile-money push, East Africa). Not certified live.

A 200 from https://service.droplinked.com/health/<provider> means the integration layer can reach that provider’s API. It does not mean a merchant can be paid through it. Treat the table above as the authority.

Stablecoin (x402)

Droplinked settles USDC on Base mainnet through the x402 protocol, and that rail is live — but only for platform-facing, agent-initiated payments today. See Agentic payments (x402) for exactly what an agent can pay for right now.

Merchant-facing x402 checkout is not available. A shop cannot currently be paid in USDC: no merchant-owned settlement destination is configured, so there is nothing for a merchant leg to settle into. Anything you read elsewhere describing turnkey stablecoin settlement for merchants is describing a roadmap, not a shipped capability. Ask us before you build against it.

Resolve availability at request time

Provider availability varies by shop and changes without notice. Do not hard-code a provider. Ask the resolver:

curl https://apiv3.droplinked.com/checkout/example-shop/payment-intent-resolver

{
  "statusCode": 200,
  "message": null,
  "data": {
    "card":   { "provider": "STRIPE", "label": "Pay with Card", "accountId": "<connected account>", "renderer": "STRIPE_ELEMENTS", "publishableKey": "pk_live_EXAMPLE" },
    "paypal": null,
    "crypto": null,
    "x402":   null,
    "wallet": [],
    "currency": { "abbreviation": "USD", "symbol": "$", "conversionRateToUSD": 1 },
    "meta": { "resolvedAt": "2026-09-20T23:29:59.092Z", "source": "shopPaymentMethodsV2", "shopId": "<shop id>", "breakerSkipped": [] }
  }
}

Rules for reading it:

A null slot means do not render that method. It is not an error and not a transient; it is the answer.
meta.breakerSkipped[] explains a method that the shop has configured but that cannot currently take money — for example {"provider":"STRIPE","reason":"PSP_ACCOUNT_NOT_READY","detail":"STRIPE_CHARGES_DISABLED"}. Codes are catalogued on Errors.
renderer tells you which UI to mount. Only the renderer values listed above are valid; treat an unknown renderer as “do not render”.
The endpoint is public — no credential needed — so you can call it before the buyer authenticates.

Merchant PSP onboarding — how a merchant connects their own account
PCI posture and card-data handling
Webhooks
Checkout intent resolver reference

Get Started

Core Concepts

Deploy & Operate

Trust Fabric Guides

Order Lifecycle

Payments

Payment Integrations

Fulfillment Integrations

Library

Platform & Architecture

Live today

Integrated, not certified live

Stablecoin (x402)

Resolve availability at request time

​Live today

​Integrated, not certified live

​Stablecoin (x402)

​Resolve availability at request time

​Related

Live today

Integrated, not certified live

Stablecoin (x402)

Resolve availability at request time

Related