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
Prefer
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).
Returns —
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-stablecoin payin and returns bank instructions and apayinId. Use a supported CAIP-2 network and the user’s wallet address as destinationAddress.
Returns —
NoahInitiatePayinResponse: { data: { payinId: string; cryptoCurrency: string; fee: NoahFeeDetails; bankDetails: BankDetails } }.
NoahFeeDetails shape: { fiatCurrencyCode: string; totalFeePct: string; totalFeeBase: string; totalFeeMin: string }.
BankDetails includes:
paymentMethodId— payment method identifierpaymentMethodType— payment rail typeaccountNumber— bank account numbercryptoCurrency— crypto currency for this payinnetwork— network identifierfee— fee breakdown (NoahFeeDetails)accountHolderName?— optional account holder namebankCode?— optional bank routing/sort codebankName?— optional bank namebankAddress?— optional bank address withstreet,street2?,city,postCode,state,countryreference?— optional payment referencerelatedPaymentMethods?— optional array of related payment methods
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.
Returns —
NoahSimulatePayinResponse: { data: { fiatDepositId: string; reference?: string } }.
getPayoutCountries
Lists countries available for fiat payouts.NoahGetPayoutCountriesResponse: { data: { countries: Record<string, string[]> } }.
getPayoutChannels
Returns payout rails available for a crypto currency.country and fiatCurrency narrow results but are optional; fiatAmount can further refine channel availability.
Returns —
NoahGetPayoutChannelsResponse: { data: { items: Channel[]; pageToken?: string } }.
Each Channel includes:
id— channel identifierpaymentMethodCategory—'Bank' | 'Card' | 'Identifier'paymentMethodType— payment rail type (NoahPaymentMethodType)fiatCurrency— fiat currency codecountry— ISO country codelimits—{ minLimit: string; maxLimit?: string }rate— exchange rate as a stringprocessingSeconds— estimated settlement timecalculated?— optional{ totalFee: string }processingTier?—'Standard' | 'Priority'issuer?— optional issuer identifierpaymentMethods?—PaymentMethodDisplay[]
getPayoutChannelForm
Loads the dynamic form schema for a channel so you can collect recipient fields before requesting a quote.
Returns —
NoahGetPayoutChannelFormResponse: { data: { formSchema?: Record<string, unknown>; formMetadata?: { contentHash: string } } }.
getPayoutQuote
Requests fees and crypto amount estimates for a payout. Includeform when the channel requires recipient data.
Returns —
NoahGetPayoutQuoteResponse: { data: { payoutId: string; totalFee: string; cryptoAmountEstimate: string; cryptoAuthorizedAmount: string; formSessionId: string; rate?: string; breakdown?: TransactionBreakdownItem[]; quote?: NoahSellQuote; cryptoCurrency?: string; fiatCurrency?: string; fiatAmount?: string; nextStep?: FormNextStep } }.
cryptoAuthorizedAmount— authorized crypto amount for the payoutrate?— effective exchange rate for this quotebreakdown?— fee breakdown array ({ type: 'ChannelFee' | 'BusinessFee' | 'Remaining'; amount: string }[])quote?— firm signed quote whenquoted: truewas requested ({ signedQuote: string; expiry: string })cryptoCurrency?,fiatCurrency?,fiatAmount?— disclosure fields echoing back the quote parameters
nextStep includes:
stepId—'Vop' | 'Cob' | 'PaymentDetails'stepType—'Ack'or'DataEntry'schema— form schema for the next step
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.
Returns —
NoahInitiatePayoutResponse: { data: { destinationAddress: string | null; conditions: DepositSourceTriggerCondition[]; ruleId?: string } }.
Each DepositSourceTriggerCondition includes:
amountConditions— array of{ comparisonOperator: 'EQ' | 'LTEQ' | 'GTEQ'; value: string }cryptoCurrency— crypto asset codenetwork— CAIP-2 network identifierdestinationAddress— destination address for the deposit
After this call returns
destinationAddress and conditions, submit the onchain transfer to satisfy them. You can do this with any wallet — including Portal’s own send method (portal.sendAsset(...)) on the same Portal instance, which builds, signs, and broadcasts in one call.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.
Returns —
NoahGetPaymentMethodsResponse: { data: { paymentMethods: PaymentMethod[]; pageToken?: string } }.
Each PaymentMethod includes:
id— payment method identifierpaymentMethodCategory—'Bank' | 'Card' | 'Identifier'paymentMethodType— payment rail typedetails— payment method details withtype, optionalaccountNumber,bankCode,last4,scheme,identifierType,identifier,routingNumber,swiftCode,bankingSystems,bankName,bankAddressaccountHolderDetails?— optional holder info withname?: { firstName: string; lastName: string; middleName?: string }issuerDetails?— optional issuer info withname?: string
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