Skip to main content

Partners API

A partner is a platform that brings its own merchants to Wava — a POS, a CRM, a marketplace, a vertical SaaS. Instead of every merchant integrating Wava separately, the partner integrates once and each merchant onboarded through the partner’s link becomes a Wava store automatically linked to the partner. Wava tells the partner about each of those merchants through the store_onboarded webhook, which carries the merchant’s merchant_key. That key is what the partner uses to process payments for that merchant.

The lifecycle at a glance

1

Wava creates your partner account

We register your partner name and issue your X-API-Key, X-API-Secret, webhook signing key and onboarding link.
2

You share your onboarding link with your merchants

The link carries your partner name: https://app.wava.co/signup?platform=YourPartnerName.
3

The integration is created automatically

When the merchant finishes onboarding, Wava resolves the platform value from the link and creates a partner integration on their store pointing back at you — no manual step for the merchant.
4

You receive `store_onboarded`

Wava POSTs to your webhook URL with the new store’s id_store, store_name, country, currency and — most importantly — its merchant_key.
5

You process payments for that merchant

Store the merchant_key and use it to create orders and payment links for that merchant. Payments emit order_payment to your webhook URL.
Full walkthrough with payloads: Onboarding Merchants.

What you get as a partner

The API secret and signing key are shown once, when your partner account is created. Store them securely — they cannot be retrieved again.

Capabilities

Partner platform endpoints

Authenticated with X-API-Key + X-API-Secret only. See Managing Merchants.

Operating on behalf of a merchant

Authenticated with the merchant’s merchant-key, which you receive in the store_onboarded webhook.
Payment endpoints are authorized by the merchant key, not by your partner credentials — the merchant key is what decides which store the order or link belongs to. See Partner Authentication for exactly which headers go on which request.

Webhooks

Your webhook URL receives both merchant-lifecycle events (store_onboarded) and payment events (order_payment, link_paid) for every merchant connected to you — you do not configure a webhook per merchant. See Partner Webhooks.

Becoming a partner

Partner access is granted case by case. Contact sales@wava.co with details about your platform and expected transaction volume.