#Márcia KP-fees
1 messages · Page 1 of 1 (latest)
Customer metadata
Sorry
Right now I'm only saving the setup_intent_id, subscription_schedule_id and charge_id on my database. Since I'm not saving the customer_id I was hoping that I could put an internal Id in the metadata and then receive it on the report
doesn't seem like it's directly possible, the reports can have columns like customer_id and customer_description and stuff but not metadata directly
you could reconcile by retrieving the Charge object and getting the customer ID from that(https://stripe.com/docs/api/charges/object?lang=node#charge_object-customer), then mapping to what you get in the report
Can I get the setup_intent_id having the customer_id
But some fees are not associated with charges
The fees from charges are ok. The problem is the ones that doesn't have the charges
Nice! Thank you. Do you know which report run type is the transaction level report?
sounds like you're on special pricing? I don't know much about how the reporting for that works(and the doc aren't public so I can't really link them)
if you have access to https://stripe.com/docs/reports/fees-reporting#transaction-level-report then that might help
Hmm ok. Thank you for your help. It would be a lot easier if we got the customer metadata though. Is there problem if we do multiple requests getting the setup intents?
Yeah I know this one. Just wanted to know the equivalent via API
there is no equivalent in the API if you have that pricing AFAIK
that's why you have to use the reporting we've built
AFAIK?
no, not really! I don't know how many of them you have or so on but you're extremely unlikely to run into rate limits if you're just serially retrieving objects from the API in a batch job
as far as I know
I can put a sleep between the requests to not spam