#binod-txn

1 messages · Page 1 of 1 (latest)

potent forum
#

👋 happy to help

#

what seems to be the issue?

jagged whale
#

I'm using stripe connect to onboard clients on my platform

#

I want to send client specific data when something is purchased from platform

#

Let's say I have two clients client1.mydomain.com (connected to stripe express account1) and client2.mydomain.com (stripe express account2). If something is purchased using stripe from these sites, I want txn statement to be client business specific

#

I'm using destination charge to create payment intent but in the txn statement I always get same business name through which I created developer account

#

does it make sense?

potent forum
#

yes actually it's expected to be this way

jagged whale
#

but it's not working as expected

#

does iDeal payment also support this?

potent forum
#

destination charges work this way

#

if you want the txn to be owned by the Connect account you should either use Direct Charges by creating the payment on the Connect Account or use the on_behalf_of field

jagged whale
#

const paymentIntent = await stripe.paymentIntents.create({ amount: price_in_cents, currency: payload.currency, payment_method_types: ['card', 'ideal'], statement_descriptor: 'Test statement!', application_fee_amount: app_fee, transfer_data: { destination: account.id } });

#

this is my paymentIntent

#

where does on_behalf_of fit?

potent forum
jagged whale
#

doc says on_behalf_of is ID of connected stripe account. Adding this will resolve the txn statement automatically?

#

so, value for destination and on_behalf_of would be same right?

potent forum
jagged whale
#

I didn't find clearly mentioned about account specific txn statement.

jagged whale
#

??

potent forum
#

sorry I'm trying to verify that the txn statement would take the descriptor of the connected account instead of the platform when using on_behalf_of

#

this is my understanding but I'm just double checking

jagged whale
#

did you check?

potent forum
#

sorry it's been really busy on discord today

#

I'm still trying to handle all of the threads sorry for keeping you waiting

jagged whale
#

okay, no worries

#

please let me know when you double check

potent forum
#

yes sure

potent forum
#

so the destination charges with on_behalf_of would work fine

runic garnet
#

@jagged whale hi i unarchived

jagged whale
#

thanks

runic garnet
#

What's your question

jagged whale
#

const paymentIntent = await stripe.paymentIntents.create({ amount: price_in_cents, currency: payload.currency, payment_method_types: ['card', 'ideal'], statement_descriptor: 'Test statement!', application_fee_amount: app_fee, transfer_data: { destination: account.id }, on_behalf_of: account.id });

#

Im creating payment intent like this. My question is, will txn statement will now be based on connected account ID?

runic garnet
#

What do you mean by txn statement?

#

Are you talking about a statement descriptor?

jagged whale
#

When someone purchase item from site, txn statement heading from platform account not from connected(express) account

#

I want connected(express) account heading in txn instead of platform business name

runic garnet
#

Ok. What type of connect account do you have

#

Oh I see you said express

jagged whale
#

I have a platform like wordpress where users can create own site and list items for sale. Im using stripe for purchasing items. So, I onboard clients stripe account (express) for each client. Problem is, on purchase, txn statement heading is my platforms business name rather than connected client account's name

runic garnet
#

Statement descriptor is set at the account level

#

Or you can set the prefix and with each PaymentIntent add a suffix

jagged whale
#

statement descriptor appears in txn details section

runic garnet
#

But using on_behalf_of will allow you to use the connect account's descriptor

jagged whale
#

I want it in txn heading

#

I have tried so many options from doc above, don't know what am I missing

#

const paymentIntent = await stripe.paymentIntents.create({ amount: price_in_cents, currency: payload.currency, payment_method_types: ['card', 'ideal'], statement_descriptor: 'Test statement!', application_fee_amount: app_fee, transfer_data: { destination: account.id }, on_behalf_of: account.id });

#

this is my code

#

??

runic garnet
#

What do you mean by txn heading

#

Where are you looking for this

jagged whale
#

after paying with Ideal payment, in ideal payment statement section

runic garnet
#

Can you share a screenshot

jagged whale
#

I want to replace Nova Automotive with connected account's name

#

statement_descriptor is displayed only after I click on list item.

runic garnet
#

Can you also share payment intent IDs associated with these transactions?

jagged whale
#

pi_3L7w4lHsW9ET26Jg0wS8ZQjc

#

this is one of my successful txn payment intent ID

#

??

runic garnet
#

Sorry have multiple threads. Will get to this in a sec

jagged whale
#

ok

#

no prob

valid iris
#

👋 I'm hopping in since @runic garnet has to head out soon - give me a minute

jagged whale
#

ok

valid iris
#

That Payment Intent ID didn't use on_behalf_of though, so I believe it's expected that it's using the platform's information

jagged whale
#

okay, so this should work? const paymentIntent = await stripe.paymentIntents.create({ amount: price_in_cents, currency: payload.currency, payment_method_types: ['card', 'ideal'], statement_descriptor: 'Test statement!', application_fee_amount: app_fee, transfer_data: { destination: account.id }, on_behalf_of: account.id });

valid iris
#

Yes, I believe that should work