Stripe Connect MAJOR Bug
After dozens of hours trying to find out why Stripe Connect is asking sellers to input keys and client IDs I get an answer from Ai. How can UNA provide a payment module that doesn't facilitate payment integration smoothly? There is no Stripe Connect payment provider in bx_payment_providers.
- Your active provider
stripehassingle_seller = 0, which is exactly the “multi-seller / sellers must supply keys” mode.
So your Stripe Connect OAuth module is not integrated into UNA’s Payments system as a provider, and there is nothing you can enable in Studio - Payments to make a Connect provider appear; it’s simply not installed/registered.
What this means right now:
- You can onboard sellers via OAuth (Connect module)
- But UNA checkout/payment processing is using the regular Stripe provider
Please fix this with an update so we can big selling with Stripe Connect.
-
- · Brand Harbor
- ·
I was able to successfully rewrite code and use sql db commands to correctly link up Stripe Connect so sellers do not have to enter Client IDs, keys, etc. Now, it connects to their existing Stripe account by entering their stripe account email address. A lot of work but so worth it for our sellers that we are going to bring onboard. whew!
-
- · Brand Harbor
- ·
When we tested the solution, it allowed a seller to connect their stripe by simply entering their email address. It allowed sellers to create subscriptions. It allowed buyers to go through a purchase. The purchase appeared in the buyers account under subscriptions. However, it did not appear in the sellers account. So, the solution did not work entirely. All it did was simplify the process of a seller to connect their Stripe account using Stripe Connect. It did not successfully match up marketplace products between seller accounts and buyers.