A minimal, deliberately ordinary Venmo integration — the configuration that selects the Firebase message-bus flow. Its only job is to show what a merchant's own callbacks do when the bus is fed a message the merchant did not send.
The flow selector in www.paypal.com/smart/buttons reaches the
Firebase bus only when all four hold. Change any one and you silently get the non-Firebase Venmo web
flow, and nothing reproduces:
| desktop | platform !== MOBILE — use a desktop browser / desktop UA |
| no popup | win falsy — don't pre-open a window |
| no onShippingChange | hasShippingCallback forces the web flow. This is
the trap: most sample integrations register it. |
| sandbox opt-in | enableVenmoQRSandbox: true. In production the clause is
!enableVenmoQRSandbox && env===SANDBOX, which is false whatever the flag is — the flag
exists only so sandbox can opt in. |
Open DevTools → Network, filter init_flow. The SDK reports its own choice.
init_flow_qr_code → you are on the Firebase bus.
init_flow_venmo_web → you are not, and any negative result here is
meaningless. Fix the four conditions above first.
Click Venmo and let the QR render. Do not scan it and do not complete any Venmo login — the bus opens as soon as the QR appears, and that it works with no buyer authentication at all is the point.
In Network, find the request to /smart/qrcode?qrPath=… and paste its
full URL here. Nothing is sent anywhere; this parses in your browser.
Also mirrored to the browser console as
[PoC] lines.