#conrad-at-pronto_api
broken edgeBOT
👋 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/1298028413113597953
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- conrad-at-pronto_api, 5 days ago, 68 messages
modern spear
Hi there
tough badger
hello
I was reporting what looks like a bug for how domains are filtered (or not filtered 😀 ) but we do have a larger underlying issue with Apple Pay sessions not being created as expected.
Can we look at that too after you have had a chance to review the filtering issues?
modern spear
Yep, we can! Taking a look at the video you shared
tough badger
Sandbox Platform account ID
acct_1Q8nLfIEeIH1gPwZ
Sandbox Connect account ID
acct_1Q8oRCIj0xieSpiY
Domain ID
pmd_1QAL7aIEeIH1gPwZxQm9AE6i
URL of the publicly accessible certificate required for apple domain verification
https://tickets.stage.seastreak.com/.well-known/apple-developer-merchantid-domain-association
Video of Apple Pay failing
https://www.loom.com/share/dc06d645231143aabb0b5d1d999942a6?sid=013b4d2d-02a4-49ad-afb5-31d7de16d221
Note: the domain we are using, tickets.stage.seastreak.com was previously used for Apple Pay transactions on the sandbox Platform account directly. And prior to that with a completely separate Stripe account (Transit Demo, acct_1Nnm3REJWlU7eFc0)
modern spear
Do you have a URL where I can test this myself? I'm getting a username / password prompt at https://tickets.stage.seastreak.com
tough badger
yes
test:seastreak-24
Maybe this old account is still causing trouble somehow...there is no option to delete the domain completely though.
modern spear
Can you share that pmd_ ID here? just copy paste from that page in the Dashboard
modern spear
I see pmd_1Ot9RpEJWlU7eFc0ywmHBWpz is disabled which should be fine
I think something else is happening here
tough badger
Yes most likely. Just wanted to share the unique history on this domain.
modern spear
If I visit https://tickets.stage.seastreak.com now, I see a publishable key for acct_1Q8nLfIEeIH1gPwZ is being used but you're also passing stripeAccount: 'acct_1Q8oRCIj0xieSpiY'. Is your goal here to use direct charges?
tough badger
The pub key ending in Pwz belongs to the Platform account
This is our first implementation of Connect Express. We have approx 5 Connect Standard merchants.
We haven't figure out yet how exactly we will be setting payments. Most likely with destination charges. That's up next. We were first trying to get Apple Pay working again since it's the default payment method in our flow for iOS and Mac OS users.
modern spear
I see, okay
tough badger
I have a story ready to go that specifies on_behalf_of --> https://docs.stripe.com/connect/charges#on_behalf_of
but without this, non-Apple Pay charges work just fine as is.
We were thinking it's an issue with Apple domain verification.
modern spear
If your goal is to test destination charges, you should remove stripeAccount: 'acct_1Q8oRCIj0xieSpiY'
tough badger
Oddlly, the Apple Pay button is displayed. Usually when Apple Pay doesn't work on Stripe the whole button is hidden.
modern spear
If your goal is to use direct charges (which we don't recommend with Express accounts), the ApplePay domain would need to be registered on the connected account directly, not the platform: https://docs.stripe.com/payments/payment-methods/pmd-registration?dashboard-or-api=dashboard#register-your-domain-while-using-connect
tough badger
If your goal is to test destination charges, you should remove `stripeAccount: '...
It is a goal in the next phase. First we were trying to get direct charges working. Is that no compatible with Express accounts?
modern spear
Not that it's not compatible but we strongly recommend against Express + direct
tough badger
yes makes sense
so do we replace stripeAccount: 'acct_1Q8oRCIj0xieSpiY' with on_behalf_of flow?
We need to do on behalf of because the end user (ferry passengers) do not know who Pronto is. They are buying from Seastreak. And the statement descriptor needs to be Seastreak.
modern spear
so do we replace `stripeAccount: 'acct_1Q8oRCIj0xieSpiY'` with `on_behalf_of` fl...
No, this wouldn't happen client side
tough badger
Are Destination and On behalf of different from each other?
modern spear
Can you share a link to the doc where that screenshot is taken from?
tough badger
There is no separate category for "On behalf of".
And this is how we are currently initiating direct charges. Which I understand we shouldn't do as Express and will change.
tough badger
If your goal is to use direct charges (which we don't recommend with Express acc...
btw, we have done this. Did you see this pic from above?
modern spear
I think this is the section you're looking for: https://docs.stripe.com/connect/destination-charges?platform=web&ui=elements#settlement-merchant
tough badger
yes that looks good. It's in our scheduled story. But how does this effect Apple Pay? We verified the connect domain.
modern spear
Hold on, let's take a step back. I think we should align on what you're looking to test and then we can get your account and domain registration in the right state
tough badger
Ok
Our current goal is just to get Apple Pay working with direct charges
We believe this should work since we verified the domain on the connect account
modern spear
Okay. In that case, can you follow these steps one more time: https://docs.stripe.com/payments/payment-methods/pmd-registration?dashboard-or-api=dashboard#register-your-domain-while-using-connect
If you make a call to list payment method domains for acct_1Q8oRCIj0xieSpiY, what do you get back : https://docs.stripe.com/api/payment_method_domains/list
modern spear
Right, okay
tough badger
how do I specify I want to see the connect merchant?
modern spear
You'll use the platform key but pass the Stripe-Account header with the connected account ID as the value: https://docs.stripe.com/connect/authentication#stripe-account-header
tough badger
let me try the Transit Demo one also
pmd_1Ot9RqEJWlU7eFc0jxb9Te77
That's in Test mode on Transit Demo
it shows apple_pay:active for ticket.stage.seastreak.com in the API response but the web app shows disabled.
the plot thickens 🍿
modern spear
In the API response for pmd_1Ot9RqEJWlU7eFc0jxb9Te77, enabled: false is what maps to the Disabled status in the Dashboard
tough badger
ok, and that automatically disables apple pay registration?
modern spear
So let's go back to acct_1Q8oRCIj0xieSpiY. There's no Payment Method Domain object here. Can you follow these steps again for the domain you want to register for use with direct charges? https://docs.stripe.com/payments/payment-methods/pmd-registration?dashboard-or-api=dashboard#register-your-domain-while-using-connect
tough badger
is there a backend resource you have access to to see that apple status for tickets.stage.seastreak.com?
sure
I've done that probably 10+ times over the last week. Will do a freshie.
modern spear
Still, keep in mind we're just testing here. You really shouldn't use direct charges with Express accounts
tough badger
agreed
Doesnt seem to take...
What about tracing apwc_1QAL4DIj0xieSpiYkF4Ybi8V ?
modern spear
Use this, not the apple_pay/domains endpoint: https://docs.stripe.com/api/payment_method_domains/create
tough badger
with platform key and stripe-account header?
modern spear
modern spear
👍
modern spear
Amazing! Thanks for being patient here, just had to make sure we took it one step at a time
tough badger
so the apple pay domain verification we were doing only works for Standard Connect accounts?
and what we did here is register the domain specifically for the sandbox account, even though the instructions say:
Live mode domains will also be registered in test mode.
modern spear
I think what you were doing before used an older endpoint. We're moving towards using /payment_method_domains instead though any previously-registered domains should still work
tough badger
gotcha
things are moving in a great direction, but admittedly it's confusing when you have both Test and Sandbox available.
If we had a choice i'd probably like to hide Test mode completely for our new accounts so its not even possible to end up there.
And only use sandboxes.
note: I started this thread pointing out the two-faced filter results:
https://dashboard.stripe.com/test/settings/payment_method_domains?apple_pay_active=false
https://dashboard.stripe.com/test/settings/payment_method_domains?apple_pay_active=true
Is that a bug? It technically cannot be both, right?
modern spear
Right, it cannot be both. Sandboxes are a bit new/still in preview so there might be something happening there