#KAS

1 messages · Page 1 of 1 (latest)

fiery shellBOT
wide maple
#

Can you give me some detail on what specific Stripe feature you're using? Are you using a third-party or getting these reports from stripe directly?

lyric wasp
#

I am downloading the report from the Stripe dashboard > Reports> Financial Reports> Payout Reconciliation

#

And again, I confess I am learning every step along the way. I know very little of the process, but I am trying to discern the source of some of the transactions so I can help our developers know what to fix so all the transactions are auto imported rather than only certain sources.

wide maple
#

Gotcha

#

And do you have an example PaymentIntent ID with payment_metadata[reference_number] set?

lyric wasp
#

If you are asking for an example of the data that might appear in that column - here are some from a recent report I was analyzing: ARMS00520938
ARMS00520940
FAPP00520813
FSSG00520734

#

Ah - I see what you were asking - sorry.

wide maple
#

I'm looking for IDs like pi_123

lyric wasp
#

No the payment intent id is blank on the fields that have the payment metadata populated

#

Let me confirm that is always true by looking at the data more

#

It appears the payment intent ID is only populated on the items that are not auto importing

wide maple
#

A Charge ID (ch_123) would also work if you see those

lyric wasp
#

pi_3MZmEjHIU60wpvgm0PJ2rkQu
pi_3MZw5IHIU60wpvgm1ZOGswXq
pi_3MZy20HIU60wpvgm1SK3IrJz
pi_3MZzUyHIU60wpvgm10omlM4h
pi_3Ma2XlHIU60wpvgm0zh2Fd5f

#

Sample from the report I am looking at of Payment Intent ID

#

And here are charge IDs:
ch_3MZmEjHIU60wpvgm0Ngy3PBS
ch_3MZw5IHIU60wpvgm1jD6DG8W
ch_3MZy20HIU60wpvgm1bKCXHzI
ch_3MZzUyHIU60wpvgm1eppRFz7
ch_3Ma2XlHIU60wpvgm0hKEsG7M

wide maple
#

Are those the charge IDs of ones that do populate payment_metadata[reference_number]?

#

That's what we really need here to understand what's going on

lyric wasp
#

Sorry - that is the charge id for ones that do not populate.

#

Let me get some from transactions that do.

#

ch_3McF9LHIU60wpvgm0vsT3qVn
ch_3MbDRiHIU60wpvgm1K092alt
ch_3Ma1pmHIU60wpvgm187tR10K

#

These are charge IDs for a few transactions that did automatically import.

#

and thereby have the payment meta data populated.

wide maple
#

Gotcha - so what this looks like is your integration is the one setting metadata[reference_number] when it creates the Charge.

#

On the examples you gave that don't set it - it looks like you're using Checkout Sessions to make payment, so ifyou want the metadata reflected there you'll need to change your code to pass in payment_intent_data.metadata.reference_number so that it also gets set

lyric wasp
#

OK - let me connect with the developers on my end to see if they understand how to make that happen. Is there documentation I should be looking to for guidance?

#

Thank you for your guidance.

manic pivot
#

You can find the docs about that here:

#

How to set metadata on the payment that gets created by a checkout session

lyric wasp
#

Thanks you!