Getting Started as a Partner

From partner creation to your first live payment in five steps.

Overview

A partner is the top-level entity in JoPay. It defines the blockchain, asset, fiat currency, branding, and webhook configuration that all merchants under it inherit. A JoPay admin creates the partner record, after which you can invite merchants, configure webhooks, and start accepting payments.

You cannot self-register as a partner. Contact the JoPay team or ask your admin to create one for you in the admin panel.

Setup Steps

Admin creates the partner

A JoPay admin opens the admin panel and creates a new partner record. They configure:

  • Chain and asset — e.g. Polygon (chain ID 137) with USDC.
  • Fiat currency — the default currency for payment amounts (e.g. USD, BRL, COP).
  • Branding — partner name, logo URL, primary and secondary brand colors.
  • Languages — primary UI language plus optional secondary languages (en, es, fr, pt).
  • Rate limits — requests per hour and per day per merchant.
  • FX rate — initial fiat-per-USDC rate and source.

Configure your webhook

In the partner portal (or via admin), set your webhook URL and secret. JoPay sends HMAC-SHA256-signed POST requests whenever a payment proof is attached or verified. See the Webhooks page for full details.

Create your first merchant invite

Generate an invite token from the partner portal or admin panel. Each invite has an optional expiry date and a max-use count (default: 1). Share the invite link with a merchant to let them onboard.

Merchant onboards

The merchant opens the invite link, connects their wallet (Sequence embedded wallet or an external EVM wallet), and completes their profile (display name, email, business details). Once onboarding is complete, the merchant appears in your portal's merchant list.

Test a payment end-to-end

Have the merchant create a test payment request from their dashboard. Open the payment link in a separate browser, connect a wallet with USDC on the correct chain, and send the exact USDC amount. Verify that:

  • The payment status moves from requested to opened.
  • Proof is attached and verified automatically via Trails.
  • Your webhook receives payment.proof_attached and payment.proof_verified events.
  • The merchant sees the payment as verified on their dashboard.

What's Next

Partner Portal

View volume, manage merchants, and configure settings.

Webhooks

Payload format, signature verification, and retry schedule.

Merchant Management

Inviting, disabling, and monitoring merchants.

FX Rates

How exchange rates are fetched, cached, and applied.