POST
cURL

Authorizations

Authorization
string
header
required

JWT bearer token. App-user tokens are issued by POST /auth/token (the partner backend calls it as its platform service account); admin and dashboard tokens are issued via OIDC login.

Body

application/json
phone_number
string
required
Example:

"9876543210"

phone_country_code
string
Example:

"+91"

contribution_channel
string | null
contributor_ref
object

A typed reference to the contributing customer, adjacently tagged on the wire as { "type": "PHONE" | "CUSTOMER_ID", "value": "…" }. Passthrough context — carried in the contributor token; the backend does not resolve the customer from it (yet).

tip_type
enum<string>

Which tip rail a contributor token is for. INDIRECT = tipped on the platform's own surface and recovered through the goal's mandate (MANDATE medium); DIRECT = paid to our merchant (PAYMENT medium), no mandate. Serde-only: carried in the token claim, never stored, since the order's medium already records the rail.

Available options:
INDIRECT,
DIRECT

Response

Token issued, or DISABLED when the caller may not collect

{ "status": "ENABLED", "contributor_token": "…" } or { "status": "DISABLED" }.

status
enum<string>
required
Available options:
DISABLED