#wololo_api

1 messages · Page 1 of 1 (latest)

modest bluffBOT
#

👋 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/1451410252120719361

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

remote prairie
#

👋 hi there, give me a moment to catch up

cosmic sedge
#

Sure aure!

#

Before getting into it.. i guess getting to use vipps at all would be priority nr 1. (vipps_preview=v1 )

remote prairie
#

Okay to answer your three questions

1) Vipps support for Connect direct charges with application_fee_amount

  • I'm unable to advice on Vipps generally because we do not have knowledge on private preview features, which requires a Stripe account to have special access. You'll need to contact Stripe Support about this. My team can advice on Stripe features that are already public.
  • That said, I understand you're building with Stripe WooCommerce Extension. This is not an extension owned us, so I do not know if application_fee_amount is supported. You can contact WooCommerce's support to ask about this. Their support contact page is here: https://woocommerce.com/document/stripe/#support (requires login to your Woo account)

2) Best way to scope charges (Stripe-Account header vs on_behalf_of)

  • In Stripe's context, Stripe-Account header is used for Direct Charges, to let Platform accounts create payments directly in the connected account. This also means that connected account themselves will be the settlement merchant (meaning on customer's bank statement, they will see your connected account business name, not your platform business name)
  • Direct charges is often used with connected account with Full Dashboard Access (so that they can manage refunds or disputes)
  • on_behalf_of also makes a connected account the settlement merchant only if the Platform is using Destination Charges, or not passing the Stripe-Account header (Seperate charge and transfers)
  • If you are already using Direct Charges, there is no need to use on_behalf_of

3) Whether using vipps_preview=v1 requires approval or a lengthy enablement process

  • I can't advice on this either, but Stripe Support should be able to. You can reach out to our support team here: https://support.stripe.com/
cosmic sedge
#

Thank for the reply. Let me catch up and think about it

#

Just to clarify: we are not using the official WooCommerce Stripe extension because it does not support Stripe Connect direct charges with application_fee_amount in a marketplace-style setup. For this reason, we are building a custom WooCommerce payment plugin that integrates directly with Stripe’s APIs

#

Understood regarding Vipps being a private preview feature. I’ll reach out to Stripe Support from the dashboard to confirm access to vipps_preview=v1.

#

The confirmation around using the Stripe-Account header for Direct Charges (and not needing on_behalf_of) is very helpful!

remote prairie
#

I see, appreciate the clarification. let me know if you have other questions!

modest bluffBOT
#

⛔️ Stripe developers have stepped away for a short while

Please leave your questions here, and we’ll respond as soon as we're back! If you need help urgently, you can contact Stripe support for help.