Fiat Payments Failing in Payment Widget Without Connected Wallet

[Onyelaudochukwuka]

error_recording.mov

When attempting an on-ramp transaction via the payment widget, I encounter the error "No wallet available for fiat payment". This happens whenever the user does not have a wallet connected.

Expected Behavior
Users should be able to complete fiat (card) payments without needing to connect a wallet first.

Actual Behavior
Fiat transactions fail if there’s no connected wallet.

Question
Is there a known workaround for this? Or is the current implementation intentionally requiring a wallet even for fiat payments?

[linear]

BLD-284 Fiat Payments Failing in Payment Widget Without Connected Wallet

[Onyelaudochukwuka]

I also reviewed the transaction prepare steps. For Stripe payments, the prepare request does return transaction steps, which I assume is why a connected wallet ends up being required for fiat payments. In contrast, the other two providers (Transak and Coinbase) do not include any steps.

That said, I noticed that the generated Stripe transaction is only executable by the seller address (with from set to 0x752b8...), rather than the account performing the checkout.

Can you confirm if this is expected behavior, or if it’s a mismatch in the SDK flow? As it stands, this effectively blocks fiat checkout since even when the buyer has a connected wallet, they cannot execute the transaction.

This issue is time-sensitive for us, so I’d really appreciate an EOD update on whether a fix is planned. The lack of response so far from the thirdweb team has been discouraging.

[joaquim-verges]

sorry fo the delay on this @Onyelaudochukwuka - we'll take a look and respond asap

[Onyelaudochukwuka]

That’s fine, I’ll await your feedback.

[joaquim-verges]

@Onyelaudochukwuka released a fix in thirdweb@5.105.47

for the 'from' address issue, since you execute transactions from the local wallet anyways, its safe to ignore that 'from' value. We'll likely remove it from the response in the future

[Onyelaudochukwuka]

Thank you for the update! 🙏 I did notice one more issue that needs attention. The wallet check tied to flatTxs.length is happening after the onramp link is opened. This means a user could complete a payment, only to return and hit a “wallet not connected” error.

To avoid that risk, the wallet validation should happen before the onramp flow is initiated. Can we get this adjusted as well?

[Onyelaudochukwuka]

@joaquim-verges

[joaquim-verges]

@Onyelaudochukwuka yep I already did this here: 778bf2c

The latest release has this change so it should be failing early in that case as expected

[Onyelaudochukwuka]

Alright, thank you!