#pckzz_connect-payment-domains

1 messages ยท Page 1 of 1 (latest)

spark wrenBOT
#

๐Ÿ‘‹ 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/1469047150632767600

๐Ÿ“ 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.

tawdry crescent
#

hello! looking at this now

cloud zenith
#

sure!

#

Question complete:
I need to add/remove payment method domains for Connect OAuth connected accounts via API, so sellers can use wallets (Google Pay, Apple Pay, Link) on their donation forms.
paymentMethodDomains.create returns success (with id and domain_name), but the domain does not appear in the Dashboard at
https://dashboard.stripe.com/acct_1RgapqJlze71f98o/settings/payment_method_domains.
paymentMethodDomains.list with stripeAccount: stripeUserId sometimes returns an empty list even after a successful create.
Is using stripeAccount correct for payment method domains on connected accounts? Which Stripe account should show these domains in the Dashboard (connected vs platform)?

tawdry crescent
#

are you creating direct charges in your use case, or are you using destination charges / separate charges and transfers?

#

if you are using direct charges, creating payment method domains with the stripe account header is the way (reference). i honestly don't interact with the dashboard all that much so i can't remember off the top of my head how the dashboard displays connected account domains, but based on some request IDs i just scraped up (e.g. req_3m9lV03KnNt6bE) it looks like you are definltey creating them successfully. can you share an example request ID from a list request that returned an empty list when you expected it to be populated?

cloud zenith
#

Billing type: We use direct charges. The PaymentIntent is created in the account connected with stripeAccount:
const paymentIntent = await stripe.paymentIntents.create(createParams, {

stripeAccount: stripeUserId
});

We don't use transfer_data or on_behalf_of. So using stripeAccount for payment method domains is aligned with our flow.

Listing request ID: We haven't yet logged the request ID of the paymentMethodDomains.list calls.

If it's important, I can add logging to the next list call and send an example request ID where the list came back empty. What do you prefer?

tawdry crescent
#

let me look through your logs real quick to see if i can spot anything obvious

#

but i guess before i do that, i want to ask

  1. have you tested this in test mode already?
  2. if so did you notice any issues displaying wallets etc after addiung the domains?
#

i want to understand if your question is about the domains not working properly or if it's exclusively about not seeing them in the dashboard / list API when you expect them

cloud zenith
#

Yes, we have tested the following behavior so far:

Our main concern is the consistency between the API and the Control Panel:

The paymentMethodDomains.create method returns success and a domain object.

In the Control Panel, under .../acct_1RgapqJlze71f98o/settings/payment_method_domains, we often don't see these domains.

The paymentMethodDomains.list method sometimes returns an empty list when we expect it to include recently created domains, because create returns success but returns nothing in the list since there is nothing in payment_method_domains (even though there was an attempt to create them).

Therefore, the main issue is that we cannot reliably view or list the domains we create, either in the Control Panel or through the listing API. This makes it difficult to confirm that the domains are being registered to the correct account and that our workflow is correct.

If you can identify anything in the logs that explains why the dashboard and list results don't match the creation responses, that would be very helpful.

tawdry crescent
#

i see 2 request IDs to the list payment method domains API on that account after the request ID i shared earlier (req_3m9lV03KnNt6bE, which was run at 2026-02-05 19:00:38 UTC)

  1. list request 1: req_LBzB0fBCrdmyu2 (from 2026-02-05 19:00:39 UTC)
  2. list request 2: req_oi2Uq4wi6jzd37 (from 2026-02-05 19:01:15 UTC)

any chance you know if either of these returned an empty value?

#

also would you mind if i log in as your platform account to look at the dashboard view? if so i can send you a link that will approve my login access

cloud zenith
#

one minute

spark wrenBOT
cloud zenith
#

register domain:
domain: backends-givefy.mqzogf.easypanel.host
id: pmd_1Sv5DZJlze71f98o5MjMMaRB
requestId: req_HSxaCxnIuQSWuL
stripeAccount: acct_1RgapqJlze71f98o
List domains (right after):
totalDomains: 1
requestId: req_ZmuMUlhAOchEj7
allDomains: Array(1)
So create and list both succeed. But the Dashboard at https://dashboard.stripe.com/acct_1RgapqJlze71f98o/settings/payment_method_domains shows "No domain added"

#

Would you need access to my dashboard? If so, how do I provide it to you?

#

in my site "success"

#

on stripe: "No domain added"

twin quiver
#

Hi ๐Ÿ‘‹

I'm stepping in as my colleague needs to go

cloud zenith
#

hey snuf! thx

#

also thx solanum!

twin quiver
#

I can see pmd_1Sv5DZJlze71f98o5MjMMaRB on the Connected Account.

#

I suspect you are not looking at the right Dashboard page but I'm not 100% certain how we display Payment Method Domains for Connected Accounts.

cloud zenith
#

Okay, sure. Perhaps there's a chance the created domain will go to the Connect platform and not to my account (acct_1RgapqJlze71f98o)?

#

i looking at acct_1RgapqJlze71f98o stripe

twin quiver
#

Unfortunately, we are not experts on the Dashboard functionality here.

spark wrenBOT
#

Hello @cloud zenith, we have sent you a direct message, please check it at https://discord.com/channels/@me/1469059142202429679

  • ๐Ÿ”— The message has instructions on how to grant read and write access to your Stripe Dashboard for our Developer Support team, in order to help you more effectively.
twin quiver
#

I can try to take a look if you grant me access

cloud zenith
#

No problem! I'd like to do this with an API to make it easier for my sellers, but that's okay, I'll go back to the manual method.

twin quiver
#

Sorry, what do you mean?

#

The registration was successful

cloud zenith
#

I have to go now, but I'll be back soon!

twin quiver
#

We close threads for inactivity so you may need to open a new one.

cloud zenith
#

Oh, okay, so all that's left is to find where it's falling, right?

#

I'm going out, but we can keep talking, I'll just be offline for a little while.

cloud zenith
twin quiver
#

I don't think I understand what you mean. The account acct_1RgapqJlze71f98o has a registered payment method domain backends-givefy.mqzogf.easypanel.host but it shows as disabled.

cloud zenith
#

ohh i got it now

#

That's strange, I'm creating it and it's showing as deactivated?

twin quiver
#

Yeah I'm trying to see why/when it changed

#

So you would need to figure out why that request was made, which explicitly passed { enabled: "false"}

spark wrenBOT
#

pckzz_connect-payment-domains

cloud zenith
#

Oooooooh, okay, I'll do it immediately when I get home.