Skip to main content
The terms below appear throughout these docs and in the API reference.

​
Partner

A partner is the business integrating with Stable Mint — you. You hold the accounts, the balances and the credentials, and you own the relationship with the people paying you.
  • Authenticates with a service account and an RSA signature on every request
  • Holds one account per currency
  • Receives webhooks for events on its own and its customers’ money
  • Manages credentials and configuration from the dashboard

​
Customer

A customer is one of your end users. You create them, you own the relationship, and Stable Mint never contacts them — what Stable Mint does is hold and attribute their money.
  • Identified by a userId that you choose and reuse across sessions
  • Requires an email address and a country code
  • May be given a virtual IBAN so incoming payments are attributed automatically
  • May carry KYC or KYB details, supplied by you
Internally, and on the wire, customers appear as partner customers — you will see it in event names like partner.customer.deposit.completed and in parameters like partnerCustomerGuid. It is the same thing. Send those identifiers exactly as the reference spells them.
See Customers.

​
Account

A currency-denominated place your money sits. One per currency, each with its own IBAN and balance. See Accounts and balances.

​
Beneficiary

A destination you have registered to pay out to — either a bank account or a wallet address. You pay out to a beneficiaryId, never to a raw account number. See Payouts.

​
Session

A time-limited context for collecting one payment from a customer. Every incoming payment belongs to exactly one session. Created with POST /v1/checkout/hosted, and expires at expiresAt. See Payment sessions.

​
Webhook

An HTTP callback Stable Mint sends to notify you about events on your account. Deliveries are signed; verify the signature before acting on one. See Receiving webhooks.

​
Idempotency key

A key you generate to make a retry safe. Sending the same key twice returns the original result rather than creating a second session, payout or deposit.

​
KYC (Know Your Customer)

Identification data for a customer who is an individual. Supplied by the partner, not collected by Stable Mint. Typically the person’s full name, citizenship and residential address, with date of birth, an identification number and a contact number as supporting detail.

​
KYB (Know Your Business)

The counterpart to KYC for a customer that is a business rather than a person. Set customerType to Business on the customer’s KYC object, and the same fields carry the company’s identity rather than an individual’s — fullName is the registered legal name, residenceAddress the registered address. Businesses additionally carry their ultimate beneficial owners. Up to five can be supplied, as uboFirstName1–uboFirstName5 and uboLastName1–uboLastName5.
A richer business record — registration number, country of incorporation, nature of business, legal form, LEI and tax identifier as first-class fields — is specified but not yet live. Today the fields above are what the API accepts.
Both KYC and KYB are passed to Stable Mint by you. Stable Mint does not collect them from your customers directly, and does not verify them in the sandbox — see Customer and Sandbox.

​
Virtual IBAN

An IBAN that routes to your account but identifies a specific customer. It is an entry point, not a separate balance. See Accounts and balances.