portal.ramps.noah. Each method sends a message to the embedded Portal iframe, which calls Portal’s Noah integration on the Client API using your client credentials. You do not call Noah’s servers directly from the browser.
For dashboard setup, signing keys, and supported CAIP-2 networks, see Noah integration overview. For HTTP shapes and webhooks, see the Noah workflow guides and Noah Business API / EMM documentation.
Prerequisites
- An initialized Portal client with the iframe ready (
onReadyor equivalent). - Noah enabled for your Portal environment and configured in the dashboard.
- For payins and payouts, the end user must complete Noah KYC with approved status before those flows succeed.
Architecture
| Layer | Role |
|---|---|
| Your app | Calls portal.ramps.noah.* |
| Portal Web SDK | postMessage bridge to the Portal iframe (do not call Mpc directly) |
| Portal iframe | Forwards to POST/GET …/api/v3/clients/me/integrations/noah/... with the Portal session |
| Noah (via Portal) | Hosted KYC, banking rails, settlement |
portal.ramps.noah over lower-level APIs. The SDK types for requests and responses live in @portal-hq/web (see the Web SDK reference section portal.ramps.noah (Noah)).
Types and responses
Successful Client API responses use an envelope{ data: T, metadata?: Record<string, unknown> }. Methods on portal.ramps.noah return Promise of that envelope (for example NoahInitiateKycResponse is { data: { hostedUrl: string } }).
Throwing or rejected promises usually indicate network errors, iframe timeouts, or API error payloads surfaced by the SDK—handle them with try/catch like other async Portal calls.
initiateKyc
Starts hosted Noah onboarding. Opendata.hostedUrl in a new browser context (for example window.open with noopener,noreferrer). Validate HTTPS and the hostname against the checkout domains Noah documents for your environment (extend the example allowlist accordingly).
| Parameter | Type | Required | Description |
|---|---|---|---|
data.returnUrl | string | Yes | HTTPS URL where Noah returns the user after onboarding. |
data.fiatOptions | { fiatCurrencyCode: string }[] | No | Fiat currencies to present in onboarding. |
data.customerType | 'Individual' | 'Business' | No | Onboarding flow variant. |
data.metadata | Record<string, unknown> | No | Opaque metadata forwarded per API rules. |
data.form | Record<string, unknown> | No | Optional prefill payload for hosted forms. |
NoahInitiateKycResponse: { data: { hostedUrl: string } }.
This call only starts onboarding; KYC outcome and status changes arrive asynchronously via Noah
Customer webhooks. See Noah webhooks.initiatePayin
Creates a fiat-to-crypto payin and returns bank instructions and apayinId. Use a supported CAIP-2 network and the user’s wallet address as destinationAddress.
| Parameter | Type | Required | Description |
|---|---|---|---|
data.fiatCurrency | string | Yes | Fiat currency code (for example USD). |
data.cryptoCurrency | string | Yes | Noah crypto asset code (for example stablecoin test symbols in sandbox). |
data.network | string | Yes | CAIP-2 chain identifier. |
data.destinationAddress | string | Yes | Address that receives crypto after settlement. |
NoahInitiatePayinResponse: { data: { payinId: string; bankDetails: Record<string, unknown> } }.
Payin lifecycle updates are asynchronous; track them with Noah
FiatDeposit and Transaction webhooks, not by polling this SDK response. See Noah webhooks.simulatePayin
Sandbox-oriented call to estimate fees or eligibility for a payin without creating a live payin. Typical body includes a NoahpaymentMethodId and fiat amount.
| Parameter | Type | Required | Description |
|---|---|---|---|
data.paymentMethodId | string | Yes | Payment method identifier from Noah. |
data.fiatAmount | string | Yes | Fiat amount as a string (decimal). |
data.fiatCurrency | string | Yes | Fiat currency code. |
NoahSimulatePayinResponse: { data: Record<string, unknown> } (shape depends on environment and product).
getPayoutCountries
Lists countries available for fiat payouts.NoahGetPayoutCountriesResponse: { data: { countries: unknown } } (format is provider-specific).
getPayoutChannels
Returns payout rails for a country and currency pair. OptionalfiatAmount can refine channel availability.
| Parameter | Type | Required | Description |
|---|---|---|---|
data.country | string | Yes | ISO country code (for example US). |
data.cryptoCurrency | string | Yes | Crypto asset code for the payout leg. |
data.fiatCurrency | string | Yes | Fiat currency for the payout. |
data.fiatAmount | string | No | Optional amount string used for filtering or quotes. |
NoahGetPayoutChannelsResponse: { data: unknown } (array or object, depending on Noah).
See also: Payouts.
getPayoutChannelForm
Loads the dynamic form schema for a channel so you can collect recipient fields before requesting a quote.| Parameter | Type | Required | Description |
|---|---|---|---|
channelId | string | Yes | Channel identifier from getPayoutChannels. |
NoahGetPayoutChannelFormResponse: { data: unknown }.
getPayoutQuote
Requests fees and crypto amount estimates for a payout. Includeform when the channel requires recipient data.
| Parameter | Type | Required | Description |
|---|---|---|---|
data.channelId | string | Yes | Payout channel id. |
data.cryptoCurrency | string | Yes | Crypto asset for the quote. |
data.fiatAmount | string | Yes | Fiat amount as a string. |
data.form | Record<string, unknown> | No | Recipient fields from the channel form. |
data.fiatCurrency | string | No | Fiat currency override when needed. |
data.paymentMethodId | string | No | Payment method hint when applicable. |
NoahGetPayoutQuoteResponse: includes payoutId, formSessionId, cryptoAmountEstimate, totalFee, and optional nextStep.
initiatePayout
Executes a payout after quoting. For crypto-sourced payouts you may need to pass depositconditions from the quote response via a trigger payload; align with Payouts and Noah’s on-chain deposit triggers.
| Parameter | Type | Required | Description |
|---|---|---|---|
data.payoutId | string | Yes | Identifier from getPayoutQuote. |
data.sourceAddress | string | Yes | Address funding the crypto leg when applicable. |
data.expiry | string | Yes | ISO-8601 expiry for the deposit authorization. |
data.nonce | string | Yes | Stable nonce for this payout attempt; reuse on retry so repeated calls stay idempotent. Must be ≤ 36 characters per Noah API constraints. |
data.network | string | Yes | CAIP-2 network for the deposit leg. |
data.trigger | NoahSingleOnchainDepositSourceTriggerInput | No | Structured trigger when Noah requires explicit on-chain deposit conditions. |
NoahInitiatePayoutResponse: { data: { destinationAddress: string \| null; conditions: unknown } }.
This call initiates the payout flow; completion and failures are reported asynchronously via Noah
Transaction webhooks. See Noah webhooks.getPaymentMethods
Returns payment methods available to the customer (for example cards or bank rails), including pagination tokens when present.NoahGetPaymentMethodsResponse: { data: { paymentMethods: unknown; pageToken?: unknown } }.
Error handling
Wrap calls intry/catch. Log or surface errors without printing full API responses in production if they might contain sensitive identifiers. Retry only for idempotent reads unless your product team confirms otherwise.
Related documentation
- Web SDK reference — Noah (section portal.ramps.noah (Noah))
- Noah integration overview
- KYC, Payins, Payouts, Webhooks
- Noah docs — API concepts
- Noah docs — authentication & signing