#james-billings_unexpected

1 messages Β· Page 1 of 1 (latest)

meager ploverBOT
#

πŸ‘‹ 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/1295313096222445631

πŸ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

tropic ocean
#

πŸ‘‹ happy to help

#

would you mind giving me more context please?

#

what's your account ID

wild copper
#

Hi, Account ID is acct_1PlVsSL0dA4cBUyd

For background, when testing BACS with our original "dev" environment, we had the same issue- BACS didn't show up on the payment element even though it was enabled. Our implementation team said that they had to enable something on the back-end in our account which confirmed we were doing mandates correctly (I think) - we're letting Stripe handle the mandate collection / emailing, no customisation here.

We've now got a second "test" environment (basically an unactivated standard account, as opposed to test-mode on our live account) and we're having the same problem.

The trouble is, support seem to have no idea what this setting is, and our implementation team aren't so contactable now as that phase is over, so I am hoping someone here might know the setting so we can point support in the right direction!

The (working) dev account is acct_1PIUh5RvKtcGlRJk

tropic ocean
#

taking a look

#

just as a side question, any reason why you created a new Standard account instead of creating different sandboxes on the same account?

wild copper
#

Hah, well, we looked at Sandboxes, but fell at the first hurdle in that we couldn't hook them up to Zuora (which is where all our transactions are driven from)

We'd love to use them but it seems they don't support "apps" like Zuora.

tropic ocean
#

ok I was able to find the ticket, I will reach out to your AE and let them take it from there. there's a missing gate on the new account, but first I need to chat with your AE to understand more about the usage and the need of that Gate in particular.

#

We'd love to use them but it seems they don't support "apps" like Zuora.
how so?

wild copper
#

There was an error a few people reported, just finding it...

#

Ah yes - β€œThis is a sandbox. Sandboxes cannot be connected to a live mode account.”
We're trying to connect a Zuora Sandbox to a Stripe Sandbox, but Stripe seems to think that it's a "liive" account.

Seems a few reports of the same error with any kind of oauth connection (not just Zuora)

tropic ocean
#

I think you can actually just skip the form

wild copper
#

Hm, the skip button looks greyed out, although it was last week my colleague tried it.

tropic ocean
#

you need to chose the sandbox first I think

wild copper
#

I'd ended up on this page, which at the bottom mentions limitations (you can't install Stripe Apps in a Sandbox) and clicking the link to that went to the Apps page which sounded very much like what Zuora does - https://docs.stripe.com/sandboxes?locale=en-GB

Test Stripe functionality in an isolated environment.

#

(the sandbox to use is selected, the "development" one under "ineligible accounts")

tropic ocean
#

oh! so Zuora is a Stripe App 🀦

#

sorry my bad I didn't catch that

wild copper
#

No worries- at least, I assume it is how the integration is done πŸ™‚

meager ploverBOT
tropic ocean
#

@wild copper I reached out to your AE they should be contacting you soon.