---
title: Merchant (Renamed → Partner Program)
description: The Merchant feature has been renamed to the Partner Program. Existing integrations continue to work.
---
# Merchant feature → Partner Program
The "Merchant" feature has been **renamed and restructured** as the **[Partner Program](/docs/partner-program)**. **Existing integrations using the old Merchant headers continue to work without code changes** — see the backwards compatibility table below.
## What changed
The previous Merchant feature is now the Partner Program, with a cleaner affiliate / revenue-share legal model. The functional surface is mostly the same, with a few simplifications.
| Old | New | Backwards compatible? |
|---|---|---|
| `X-Merchant-Id` header | `X-Partner-Id` (canonical) — `X-Merchant-Id` is now a legacy alias | ✅ Yes |
| `X-Merchant-Wallet` (per request) | Accepted but ignored — payout destination is on the Partner record | ✅ Yes (no-op) |
| `X-Merchant-Fee-Percent` (per request) | Accepted but ignored — pricing tier is on the Partner record | ✅ Yes (no-op) |
| Per-request fee % | Fixed tier set at onboarding (0/5/10/15/20%, default Tier 2 = 10%) | Existing partners migrated individually |
| Weekly on-chain settlement | Monthly commission paid by Agnic from its own accounts payable | Partners receive notification of new payout schedule |
## Do I need to migrate?
**No.** Existing integrations using `X-Merchant-Id` continue to work. Your existing code does not need to change.
If you want to use the new canonical header name `X-Partner-Id`, you can. Both names point to the same thing.
The `X-Merchant-Wallet` and `X-Merchant-Fee-Percent` headers are still accepted (so your existing code does not error) but they no longer drive behaviour — the new model uses the Partner record for both payout destination and pricing tier.
Full Partner Program documentation
View commission accruals and confirm your tier