mdcopley08

[thorn sandal]

If we pull all Charges made on all accounts (platform and connected) on a daily basis and populate metadata, will that always be the source of truth for all payments we've accepted?
When you say "source of truth", what do you mean? I don't understand what's being asked here

If we can still use Charges as a source of truth (and charge metadata), is there any way to view charge metadata in the Stripe dashboard? I thought it defaulted to viewing the PaymentIntent and then we could click to get to the related Charge, but now I only see py_ links and there doesn't seem to be a way to get to the PaymentIntent or Charge webpage to view the metadata
You can only view charge metadata via the API. If you're using Payment Intents, then you can put metadata on the Payment Intent and view that via the Dashboard.

[worthy grove]

Okay got it, and for the first question I'm trying to understand what the "py_" pages/objects are

When I click on a charge I expect to see a PaymentIntent link but I'm noticing a new "py_" page now, here's an example: https://dashboard.stripe.com/connect/accounts/acct_1LjmFP33LknuOx3i/payments/py_1LpDml33LknuOx3iViJX0nPR

[thorn sandal]

The py_ objects are basically the same as the ch_ objects. They are often used interchangeably

[worthy grove]

Are they different at all?

I have an integration that relies solely on a Charge Id in the format of ch_ being created every time we get payment - is there any issue there or do I need to also be looking for py_ ?

For example - in some cases will a Charge object not get created but a py_ object will get created

[thorn sandal]

py_ is commonly used for non-card payments methods such as ACH, Bancontact, SEPA, iDEAL, etc and/or payments from the Connect Platform to the Connect sub-account