Partner Merchants

Create a referred merchant from your own signup flow

For a platform whose merchants sign up on your side rather than ours.

Creates an unverified account, a DRAFT business and a pending link, and returns a claim URL to send the merchant.

What it does not do: issue a password, send a one-time code, or earn you anything yet. The merchant opens the claim URL, sets their own password and verifies their own phone — and that verification is the only thing that activates the link and starts commission. You cannot consent on their behalf.

An existing SwiftPayIQ phone number is refused rather than claimed: invite that merchant through the connection flow instead.

post/partner/merchants

Request

  • Base URL: https://api.swiftpayiq.com/api/v1
  • URL: https://api.swiftpayiq.com/api/v1/partner/merchants
  • Auth: HTTP bearer

Request body

phonestring required

The merchant's own phone, E.164.

namestring required
emailstring nullable
attestedConsentboolean required

You are asserting the merchant asked you to do this. Recorded on the consent trail against your partner account, with the key on the audit entry. Required.

Example request

{
  "phone": "+9647701234567",
  "name": "اسم صاحب النشاط",
  "attestedConsent": true,
  "business": {
    "commercialNameAr": "متجر الأمل",
    "governorate": "BAGHDAD",
    "businessPhone": "07711111111"
  }
}

Response

Created. Send claimUrl to the merchant — nothing happens until they use it.

referredOwnerAccountIdstring
businessIdstring
linkIdstring
claimUrlstring

Example response

{
  "claimUrl": "https://my.swiftpayiq.com/register?phone=%2B9647701234567"
}

Changes

No recorded changes to this operation across all 1 revision of this API.