Safepay performs KYC/KYB on every merchant. Payments remain blocked until the merchant status becomes
ENABLED.- One aggregator merchant can link to only one Raast merchant.
- A single Raast merchant can be shared across many aggregators. This lets a business entity use multiple aggregators without re-onboarding.
Create a merchant
Use the Aggregator Merchants API to create and link a merchant. Replace placeholders with your real values. The header name must match the OpenAPI security scheme (X-SFPY-AGGREGATOR-SECRET-KEY).
Keep the returned
data.token in your vault. Safepay refers to it as the aggregator_merchant_identifier when you create payments, QR codes, refunds, and payouts.Merchant lifecycle
- Created - Safepay receives your request and assigns an ID.
- Pending checks - KYC/KYB validations run. Provide documentation if requested.
- Enabled - Payment, QR, and payout endpoints accept this merchant.
- Disabled - Safepay can suspend a merchant; payment requests will fail until re-enabled.
List merchants and Get merchant endpoints to monitor these transitions during onboarding.