yokogi_best-practices

[cosmic spade]

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

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

[slim pulsar]

Please can you just summarise the Qs here. It's not clear what the ask is from your doc

[gleaming sequoia]

First, I would like to know the procedure for enabling convenience store payments on the dashboard using a Standard linked account.

I would also like to know the procedure for confirming whether convenience store payments are enabled for a linked account. Is it sufficient to obtain the latest account status via API and check whether the capability konbini_payments is active?

I am asking this question because I would like to know the reason why the capability is not enabled even though it is enabled in the test environment, as shown in the current image.

If it is difficult to understand, please let me know if you need any further information.

[slim pulsar]

First, I would like to know the procedure for enabling convenience store payments on the dashboard using a Standard linked account.
I assumed you mean connected accounts? In any case, if you're the platform you can control the available payment methods for your connected accounts via the Dashboard: https://docs.stripe.com/connect/dynamic-payment-methods?connect-payment-integration-type=checkout&connect-charge-type=direct&connect-dashboard-type=full&on-behalf-of=false

I would also like to know the procedure for confirming whether convenience store payments are enabled for a linked account. Is it sufficient to obtain the latest account status via API and check whether the capability konbini_payments is active?
Yes, that will infer whether the account can process Konbini payments. There are corresponding account.* and capability.* events that fire when those change

I am asking this question because I would like to know the reason why the capability is not enabled even though it is enabled in the test environment, as shown in the current image.
Not sure what you mean. Test mod behaves slightly differently than live mode in regards to capabilities. There's no blocking requirements in test mode, so we may require additional verification info from those accounts before it can be enabled. This is explained here: https://docs.stripe.com/connect/payment-methods

[gleaming sequoia]

What concerns me now is that even though I enabled convenience store payments in the test environment, konbini_payments is not added to capability. This is a difference between test mode and live mode. If I enable convenience store payments from the dashboard in the production environment, will it be displayed in capability as expected?

[slim pulsar]

Which account ID are you looking at?

[gleaming sequoia]

The account ID is acct_1RnxGGHCcKfveQXN.
This is a test environment account.

[slim pulsar]

It's because there are requirements outstanding on the account before Konbini can be enabled. See this account.updated event: https://dashboard.stripe.com/test/events/evt_1RnzchHCcKfveQXNqoEy2yI6

Look in requirements hash, specifrically:

          "settings.konbini_payments.support_email",
          "settings.konbini_payments.support_hours.end_time",
          "settings.konbini_payments.support_hours.start_time",
          "settings.konbini_payments.support_phone"
        ],```

You need to set those values on the account via the API

[gleaming sequoia]

"currently_due": [
          "settings.konbini_payments.support_email",
          "settings.konbini_payments.support_hours.end_time",
          "settings.konbini_payments.support_hours.start_time",
          "settings.konbini_payments.support_phone"
        ],

We would like to enter that information via the dashboard review process or the form hosted by Stripe, rather than via the API.
The reason for this is that we are using Stripe's hosted form to create linked accounts, so we want to maintain consistency and reduce the amount of work involved.

If we proceed with the review on the dashboard in the production environment, will Stripe collect this information as well?

[slim pulsar]

I'm not sure if/how that can be collected in our Dashboard

[gleaming sequoia]

In the production environment, if we enable convenience store payments from the dashboard using the Standard linked account, we can confirm that the konbini_payments capability is active. Is this understanding correct?

If so, we will give up on testing in the test environment for now and proceed on the assumption that it will work in the production environment.

[slim pulsar]

In the production environment, if we enable convenience store payments from the dashboard using the Standard linked account, we can confirm that the konbini_payments capability is active. Is this understanding correct?
Depends if the accounts have those required fields I outlined above. You can see what required info is needed for Konbini capability here: https://docs.stripe.com/connect/required-verification-information#JP+JP+none+full+individual+konbini_payments