#Arora-Connect

1 messages · Page 1 of 1 (latest)

midnight junco
#

Hi there, is this a question about PaymentIntent's statement descriptor ?

wise sluice
#

Hello Jack, we populate statement descriptor, suffix, name and description on the payment intent and on line items, we populate name and descriptions with in the product data (as a new in line product) however the connected account which receives these payments don't display these descriptions when requested using balance transactions api.

midnight junco
#

can you share with me the balance transaction ID?

wise sluice
#

Sure will share shortly. In the mean time, please see the screen shot that shows an activity on a connected account activity and the description is shown as payment from arora, we were hoping it could be more helpful to show our product description here but we couldn't find a way to do it.

midnight junco
wise sluice
#

I could be wrong but I believe we did it also, however it doesn't display under balance transactions, could you check this txn_1KqxSn8aQOyZ6eawRynO6d3s please?

#

You may notice description being null

#

If we were to populate the description or Metadata with custom key value pairs, would it be possible to do it part of payment intent during session checkout call I.e session create api?

midnight junco
wise sluice
#

Sure, just double checking, but will this Metadata show up in the balance txns api call if we do so?

midnight junco
#

No it won't, the metadata will be attached to the payment_intent object, not the balance transaction.

#

Hmm, I'm afraid that I can't think about a solution right now. can you write it to Stripe support https://support.stripe.com/contact and mention that you have discussed this with Discord engineer, and they will forward your ticket to us.

wise sluice
#

Sure Jack, thanks for your help today. I will send our detailed query and our challenge around the balance transactions.

midnight junco
#

Thanks for the understanding and sorry I can't resolve the issue in time. Please remember to include all relevant sources IDs and request IDs in your ticket.