Skip to main content
​
Week of June 12, 2026
NewImproved

​
Partner JWT face-scan verification

Partners can now launch users straight into biometric face-scan verification using target: "naattech" in the JWT launch flow. MXN ramps require biometric verification before fiat transfers are enabled.

​
Agreement signing via launch flow

Launch users directly into electronic-signature and terms-and-conditions agreement flows using target: "agreements" in the user launch flow. Works with both Firebase and partner JWT authentication.

​
Auth token access and refresh pairs

POST /auth/token now returns an access token and a refresh token. Use the refresh token to obtain a new access token without re-signing a JWT:
{
  "access_token": "<jwt>",
  "token_type": "Bearer",
  "expires_in": 3600,
  "refresh_token": "<token>"
}
This builds on last week’s auth token endpoint; the JWT authentication guide covers the full flow.

​
PT wrap and unwrap orders on Solana

Partners can now execute Principal Token wrap and unwrap orders on Solana using the existing /ramp/quote and /ramp/order flow with PT asset identifiers — the testing swaps guide walks through it.

​
Onboarding auto-creates organization

When a new user completes onboarding, an organization is created for them automatically — partners no longer need to call POST /ramp/organization separately after signup.

​
KYC submission validates required fields

POST /ramp/customer/{customer_id}/kyc now validates required personal fields up front — email, phoneNumber, occupation, name, dateOfBirth, and a full address. Mexican customers (address.country: "MX") must include a CURP; an RFC is optional. Missing or invalid fields return 400 with a list of what to fix, as detailed in the onboarding guide.Errors from POST /auth/token and the JWT launch flow now include an error_uri (OAuth 2.0) that points to the matching entry in the authentication errors guide, so you can jump straight to the cause and fix.
​
Week of June 5, 2026
NewImproved

​
Auth token endpoint

The new POST /auth/token endpoint issues access tokens for server-to-server calls — prefer it over launch-flow JWTs when you need backend-only access, as described in the JWT authentication guide.

​
Scoped API key enforcement

API keys now enforce scope-based access control: keys created after June 8 default to minimal scopes, while existing keys keep working unchanged. The authentication reference explains the scope model.

​
Bank compliance webhook signal

The bank_account_updated webhook now signals when a bank needs additional verification: while compliant is false, the bank can’t be used until the customer completes the verification flow.

​
NaatTech biometric verification

Identity verification now supports NaatTech biometric face-scan — the foundation for the partner JWT launch flow.

​
Partner JWT auth launch

The partner dashboard can now launch users via partner-issued JWTs, so you can authenticate users with your own identity provider, as set up in the JWT authentication guide.
​
Week of May 29, 2026
NewImproved

​
JWKS-based JWT verification

Partners can now register a JWKS endpoint for JWT-based authentication: the platform fetches and caches public keys from your /.well-known/jwks.json endpoint to verify partner-issued tokens, as described in the JWT authentication guide.

​
PT token metadata improvements

The partner dashboard now shows token metadata for all rampable assets, not just those currently held, improving asset selection when initiating quotes.
​
Week of May 22, 2026
Improved

​
Better KYB error messages

KYB validation errors now return structured, field-level messages instead of generic failures, so partners get clearer guidance when a submission is incomplete or invalid.
​
Week of May 15, 2026
NewImproved

​
Self-service API keys

Approved organizations can now generate their own API keys directly in the dashboard — no more requesting access over Slack. Once your organization is approved through KYB, create keys from your account settings; the authentication reference covers usage. In sandbox, organizations created through the portal are auto-approved, so you can generate keys and run the full flow immediately, as noted in the test environment guide.

​
KYB questionnaire renderer

KYB questionnaires now render dynamically based on organization type and jurisdiction, replacing the previous static form layout.
​
Week of May 8, 2026
NewImproved

​
Client portal document upload

Customers can now upload KYB-required documents directly through the client portal during onboarding, removing manual document collection outside the platform.

​
Onboarding requirement progress

The onboarding flow now shows requirement-completion progress, so customers see exactly which steps remain before their organization is approved.

​
Entity editing and tax ID population

Organization entity details and tax identification numbers can now be edited after initial submission, so customers can correct mistakes without re-creating the organization.