portal.ramps.noah. Each method issues HTTP requests through portal.api to Portal’s Noah integration on the Client API using your client API key. You do not call Noah’s servers directly from the app.
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
Portalclient with a wallet and API access. - 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. All request and response types live in io.portalhq.android.api.data.noah.
Supported networks
Everynetwork parameter takes a CAIP-2 chain identifier. Use the constants on NoahNetwork rather than string literals so a typo is a compile error instead of a runtime failure.
Any other value is rejected with a 400 Bad Request (
PortalException.Api.HttpBadRequest), because the chain is not mapped to a Noah network. A non-CAIP-2 string such as "Ethereum" is rejected earlier still, by the [namespace]:[reference] format check. Read the specific reason from the exception’s rawBody rather than matching on message text — the wording is not a stable API.
Types and responses
Every response is an envelope —data class NoahXxxResponse(val data: T, val metadata: NoahResponseMetadata? = null), where NoahResponseMetadata is a type alias for Map<String, Any>.
All nine methods are suspend and return Result<T>. They do not throw, and they do not return a bare value. Handle both outcomes with onSuccess / onFailure:
onSuccess / onFailure, getOrNull(), or getOrThrow(). Do not wrap these calls in try/catch — the failure is inside the Result, not on the stack. See Error handling.
initiateKyc
Starts hosted Noah onboarding. Opendata.hostedUrl in the system browser. Validate HTTPS and the hostname against the checkout domains Noah documents for your environment (extend the example allowlist accordingly).
The
returnUrl must be an HTTPS URL. Custom app schemes (for example myapp://callback) are not supported. For mobile applications, the recommended pattern is to use an HTTPS bridge page that redirects to a deep link after KYC completion.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 network and the user’s wallet address as destinationAddress.
Returns —
NoahInitiatePayinResponse: { data: { payinId: String, bankDetails: NoahBankDetails } }.
NoahBankDetails includes:
paymentMethodId— payment method identifierpaymentMethodType— payment rail type, for exampleBankSepaorIdentifierPixaccountNumber— bank account numbercryptoCurrency— crypto currency for this payinnetwork— network identifierfee— fee breakdown (NoahFeeDetails:fiatCurrencyCode,totalFeePct,totalFeeBase,totalFeeMin)accountHolderName— optional account holder namebankCode— optional bank routing or sort codebankName— optional bank namebankAddress— optionalNoahBankAddresswithstreet,street2,city,postCode,state,countryreference— optional payment referencerelatedPaymentMethods— optionalList<NoahBankToAddressRelatedPaymentMethod>
Payin lifecycle updates are asynchronous; track them with Noah
FiatDeposit and Transaction webhooks, not by polling this SDK response. See Noah webhooks.simulatePayin
Simulates a fiat deposit landing against a payment method so you can exercise the payin flow end to end without moving real money.
Returns —
NoahSimulatePayinResponse: { data: { fiatDepositId: String, reference: String? } }.
getPayoutCountries
Lists countries available for fiat payouts, keyed by ISO-3166 country code with the fiat currency codes supported in each.NoahGetPayoutCountriesResponse: { data: { countries: Map<String, List<String>> } }.
getPayoutChannels
Returns payout rails for a given crypto asset. OnlycryptoCurrency is required; country and fiatCurrency narrow the results, and fiatAmount seeds channel-level fee calculations.
Returns —
NoahGetPayoutChannelsResponse: { data: { items: List<NoahChannel>, pageToken: String? } }.
Each NoahChannel includes:
id— channel identifierpaymentMethodCategory— broad grouping such asBank,Card, orIdentifierpaymentMethodType— payment rail type, for exampleBankSepaorIdentifierPixfiatCurrency— fiat currency codecountry— ISO country codelimits—NoahChannelLimitswithminLimitand optionalmaxLimitrate— exchange rate as a stringprocessingSeconds— estimated settlement timecalculated— optionalNoahChannelCalculatedwithtotalFeepaymentMethods— optionalList<NoahChannelPaymentMethodDisplay>, only populated when a customer id was suppliedprocessingTier— optional settlement speed tier such asStandardorPriorityformSchema— optional inline JSON Schema for the channel’s payout formformMetadata— optionalNoahFormMetadatawithcontentHashissuer— optional issuer identifier
getPayoutChannelForm
Loads the dynamic form schema for a channel so you can collect recipient fields before requesting a quote. ThechannelId is URL-encoded as a single path segment, with spaces normalized to %20.
Returns —
NoahGetPayoutChannelFormResponse: { data: { formSchema: Map<String, Any>?, formMetadata: NoahFormMetadata? } }.
getPayoutQuote
Requests fees and crypto amount estimates for a payout. Includeform when the channel requires recipient data.
Choosing the amount denomination
fiatAmount and cryptoAmount are mutually exclusive. The primary constructor enforces this at runtime — passing both, or neither, throws IllegalArgumentException at construction, before any network call:
NoahGetPayoutQuoteResponse: includes payoutId, totalFee, cryptoAmountEstimate, cryptoAuthorizedAmount, formSessionId, and optional cryptoCurrency, fiatCurrency, fiatAmount, rate, breakdown, quote ({ signedQuote, expiry }), and nextStep.
Each breakdown entry is a NoahTransactionBreakdownItem with a type of ChannelFee, BusinessFee, or Remaining, plus an amount.
Set
quoted = true if you intend to submit the payout with a NoahQuotedOnchainDepositSourceTriggerInput trigger — that variant requires the signedQuote returned here.initiatePayout
Executes a payout after quoting. Returns the destination address and the on-chain deposit conditions your transfer must satisfy.java.time requires API 26 or core library desugaring. If your minSdk is lower and desugaring is not enabled, format the expiry with a UTC SimpleDateFormat instead.
Returns —
NoahInitiatePayoutResponse: { data: { destinationAddress: String?, conditions: List<NoahDepositSourceTriggerCondition>?, ruleId: String? } }.
destinationAddress is nullable because it is derived from conditions[0].destinationAddress and falls back to null when that shape is missing. ruleId is returned for permanent and quoted triggers.
Deposit source triggers
The payout must be authorized by a trigger. Either supply one explicitly, or rely on a saved payment method attached to the quote viapaymentMethodId — when trigger is omitted and the saved method is a single on-chain deposit source, a default trigger is synthesized from the sourceAddress, expiry, and nonce you passed.
NoahOnchainDepositSourceTrigger is a sealed interface with three implementations:
Each implementation defaults its
type property to the correct discriminator, so you do not need to set it:
Type, Conditions, SourceAddress, Expiry, Nonce) to match the Noah API wire format. The same applies to NoahBusinessFee, whose fields serialize as FeeBase, FeePct, and FiatCurrency — visible in any logged request body.
After this call returns
destinationAddress and conditions, submit the on-chain 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 the saved payment methods available to the customer for payouts, including a pagination token when more results exist.request parameter is defaulted, so you can call it with no arguments to use server-side defaults:
Returns —
NoahGetPaymentMethodsResponse: { data: { paymentMethods: List<NoahPaymentMethod>, pageToken: String? } }.
Each NoahPaymentMethod includes id, paymentMethodCategory, country, and displayDetails, plus optional customerId, capabilities, accountHolderDetails, and issuerDetails.
Error handling
Every Noah method returnsResult<T>. Failures are captured inside the Result rather than thrown, so handle them with onFailure, fold, or getOrElse — not try/catch.
The following exceptions may appear in a failed Result:
HttpRequestFailed.statusCode is null when no valid HTTP response was received, or for synthesized failures such as a 200 body that carried an error envelope. A null statusCode therefore means “no status to branch on”, not “unknown error”.
Related documentation
- Android SDK API reference — generated KDoc for
io.portalhq.android.ramps.noah - Noah integration overview
- KYC, Payins, Payouts, Webhooks
- Noah docs — API concepts
- Noah docs — authentication & signing