fflowcoin_crypto-onramp-error

[weary wind]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1500912410951684269

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[wintry niche]

Hello 👋

Can you provide a link to the doc for the specific Onramp you are following?

[obsidian bluff]

Three pages, not one — I pulled from each:

1. API reference (primary): https://docs.stripe.com/api/crypto/onramp_sessions/create — used for the wallet_addresses,
   destination_currency/currencies, destination_network/networks, lock_wallet_address, customer_ip_address,
   source_amount/currency parameter shapes.
2. Embedded onramp guide: https://docs.stripe.com/crypto/onramp/embedded — used for session lifecycle (initialized →
   requires_payment → fulfillment_processing → fulfillment_complete) and the validation error codes
   (crypto_onramp_invalid_destination_currency_and_network_pair, crypto_onramp_no_wallet_address_to_lock,
   crypto_onramp_wallet_addresses_not_all_networks_supported).
3. Onramp product overview: https://docs.stripe.com/crypto/onramp — high-level integration types (Embedded vs. Hosted
   vs. Embedded Components vs. Headless). Used to confirm we're on the standard Embedded path.

Important caveat: the API ref page (#1) lists base as a valid destination_network enum and implies the same key in
wallet_addresses, which is what led me to send wallet_addresses[base] and get rejected with parameter_unknown. The
empirically-correct key is wallet_addresses[base_network]. Stripe's docs and Stripe's API parser disagree here — that
contradiction is in the support ticket and called out in memory/reference_stripe_onramp_wallet_key.md.

[wintry niche]

In this case I'm looking for the integration guide and that would be the embedded crypto onramp doc you shared. That's our start as that determines how you should shape your API request. Taking a look now

And where exactly in the flow are your customers getting stuck?

[obsidian bluff]

"Review your order"

[wintry niche]

Do you have an onramp session ID for one of these failing sessions?

[obsidian bluff]

cos_1TSzzkF7tTUMTiTnn7rjrh4Z as the primary repro (it's the freshest and
shows the customer-visible Review-order error path) and cos_1TT6niF7tTUMTiTn1A1T7dUw as the secondary (proves the bug
isn't in our request shape — same failure with their ideal params).

[wintry niche]

Okay so two things:

• This is still a preview feature so the team that staffs this Discord server is not going to be very familiar with it. I'm just trying to do what digging I can and provide you with more details you can use in your ongoing case with Stripe Support
• The error codes I am seeing (so far) appear to suggest an error with a partner zerohash_api_error

[obsidian bluff]

1. "What is the full Zero Hash error response?" Stripe's logs should show the exact zerohash_api_error code/message
   string returned by Zero Hash, not just the category. The string usually contains things like customer_kyc_failed,
   entity_not_provisioned, asset_not_supported, limit_exceeded, geo_restricted.
2. "Is acct_1L3N9rF7tTUMTiTn provisioned on Zero Hash's side?" Stripe's internal team can check whether we have a Zero
   Hash entity ID linked to our Stripe account.
3. "Is USDC-on-Base enabled for our Zero Hash entity?" Per-asset enablement is common.
4. "What are the per-transaction and aggregate limits on our Zero Hash entity?" If they're $0 or unset, every order
   fails.
5. "Does our Zero Hash provisioning require any additional attestations or addenda we haven't signed?"

[wintry niche]

1. The API response from ZeroHash has error_message="{"error":"Cannot generate quote for disabled participant"}"

For the rest:
This isn't something I can check here. As I said, there is limited familiarity with the crypto onramp integrations by staff on this server

[obsidian bluff]

Thank you.

[wintry niche]

Our support team should be able to help iron this out, but I understand it's not a smooth process. As far as I can tell, there's nothing wrong with how you are integrating with the Stripe APIs.

[weary wind]

fflowcoin_crypto-onramp-error