waynek_api

[grand scroll]

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

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

[restive abyss]

Hi there

Sorry, I don't quite follow. What do you mean by "the Stripe payment element has a table with four columns"?

[dusty wagon]

This thing:

const instance = loadConnectAndInitialize({
                publishableKey: PUBLIC_STRIPE_KEY,
                fetchClientSecret: clientSecret,
                appearance: {...

const payments = instance.create('payments')
            document.getElementById("stripe-payments-container")!.appendChild(payments)
...```

It's on the connected account user's account management page on our website.

[restive abyss]

Ah gotcha, okay. You're working with Connect Embedded Components

[dusty wagon]

Yes, sorry I don't remember all the names of the Stripe things.

[restive abyss]

No worries, it's hard to keep them all straight for me, too 😅

To make sure we're on the same page, which components are you setting when creating an AccountSession? https://docs.stripe.com/api/account_sessions/create#create_account_session-components

[dusty wagon]

I've got this,

                account_onboarding: { enabled: true },
                account_management: { enabled: true },
                balances: {
                    enabled: true,
                    features: {
                        instant_payouts: false,
                        standard_payouts: false,
                        edit_payout_schedule: false,
                    },
                },
                documents: { enabled: true },
                notification_banner: { enabled: true },
                payment_details: {
                    enabled: true,
                    features: {
                        destination_on_behalf_of_charge_management: false,
                        refund_management: true,
                        dispute_management: true,
                        capture_payments: true,
                    }
                },
                payments: {
                    enabled: true,
                    features: {
                        destination_on_behalf_of_charge_management: false,
                        refund_management: true,
                        dispute_management: true,
                        capture_payments: true,
                    }
                },
                payouts: {
                    enabled: true,
                    features: {
                        edit_payout_schedule: false,
                        instant_payouts: false,
                        standard_payouts: false
                    }
                },
                payouts_list: { enabled: true }
            }```

[restive abyss]

So in this case, I think the "From" field should only be populated if that particular PaymentIntent is tied to a Customer object and that Customer object has an email or name

Taking a step back though, let's take a look at the example PaymentIntent you shared: pi_3QgVMFGhzXBKOMCr1X9J4k8j

For this PaymentIntent, what exactly about this PI do you want to be visible within the Payments embedded component?

[dusty wagon]

If either the name or the email showed it would be possible to identify which payment is for who's booking.

Ideally it would be a booking reference so it would be unique, but email or name is good for now.

[restive abyss]

I deleted the image since this is a public conversation and the image included email addresses

[dusty wagon]

Ok thank you.

[restive abyss]

Gotcha, okay. So in this particular case, the name and email you see in the Dashboard are related to what we call guest customers: https://support.stripe.com/questions/guest-customer-faq

This is our way of grouping similar payments together but this PaymentIntent wasn't created for a specific Customer object

That's kind of going into the weeds a bit/tangential to your actual question. Currently, it's not possible to edit the columns we show in the Payments embedded component.

I'll provide this feedback to our team in case this is a feature we can build in the future.

As for tying PaymentIntents back to order records in your database, I recommend using metadata on PaymentIntents to do this. This doesn't solve the issue of the embedded component but would at least give you a way to programmatically search

Here's an example: https://docs.stripe.com/metadata/use-cases#the-search-api

[dusty wagon]

I see what you're saying. I did start off adding meta data in fact. I was hoping the payment element might 'just handle it' but it looks like I need to make a custom table in order to shoe the relevant information then do you think?

*thanks for the link, I didn't know about meta data and the search api.

[restive abyss]

Right, at least for now since the embedded component doesn't surface this information at the moment

[dusty wagon]

Thank you for your help, I'm glad to know where I'm at.