FRtech, In the recent pretest of Venmo the Online team saw low campaign conversion rates around ~37%. vs 70-80% with all of our other payment methods and indicates drop off by the donors. This is a poor showing for this payment method and we'd like to explore how to improve this. There is an issue detected where Venmo has flow problems when the donor is checking out in a non-native browser. It is unclear to the donor on how to get back to Wikimedia when they are checking out with Chrome on an Apple device and any other non-native browser on the local device. They get too far into the flow to back out when they can't complete the donation with Venmo and it is confusing. Peter Coombe looked at this and we reached out to Venmo to understand more about why. Here are the relevant points we learned:

-WMF wonder why Venmo doesn't check for browser features. “(https://developer.mozilla.org/en-US/docs/Web/HTTP/Browser_detection_using_the_user_agent). To work around the above, it seems WMF would have to constantly update the user agent. Venmo responded to indicate that they do use window.navigator.userAgent to detect which browser Venmo is in.

• However, the issue is that we don't have access to the isBrowserSupported function in the banners, since we can only load Venmo's code on our payments site.The issue is that we don't have access to the isBrowserSupported function in the banners on donate Wiki, since we can only load Venmo's code on our payments site and not on donate Wiki.

-If Venmo won't work in a user's browser, ideally WMF would like to hide it as an option in the banner. However, as above, we can not load third-party javascript in the banners on wikipedia.org, so the isBrowserSupported method is not available there. Peter had thought we might be able to roll our own code for this, but it looks like quite a complicated series of checks that Venmo is doing for browser support.

-The Venmo SDK team mentioned that the browser detection library used by isBrowserSupported() is open source, and WMF can use this to perform our own browser detection without having to load the BT javascript library in the banners:
https://github.com/braintree/browser-detection/tree/main

-The Venmo SDK team also mentioned that they are also doing an additional check for Venmo by combining 2 modules that are exported from the browser detection library to hide it if it browser is iOS Chrome. There seems to be a bug related to Venmo on iOS Chrome that they are working on, so they have removed Venmo from being presented in that scenario.

Can we explore if either of the approaches Venmo mentions is workable to improve this flow? The next pre-test is planned for ~ 14-15 Oct approximately. We'd like to improve the experience.