Bo0013246

[hasty perch]

1. They're explained here: https://stripe.com/docs/api/balance_transactions and https://stripe.com/docs/api/charges. Charges are just a type of payment.
2. Not sure. We're not dashboard experts in here

You can list balance transactions with the api here: https://stripe.com/docs/api/balance_transactions/list

[hardy copper]

Thanks, I am still not following the difference between charge and balance transaction, how can I understand it intuitively?

also, i the available_on from balance_transaction always going to hold true?

are there cases where that is not true?

[hasty perch]

Balance transactions represent changes to your account's balance. So one is created for every payment, payout, etc

A charge is just that

A charge a customer pays you

[hasty perch]

You're asking if that date is always going to be accurate?

[hardy copper]

yes

[hardy copper]

ok, what about a payment?

[hasty perch]

What do you mean?

What about payments?

[hardy copper]

the difference between charge and payment

[hasty perch]

A charge is a payment, as I stated earlier

And available_on should be accurate, but there may be edge cases where it isn't

[hardy copper]

so why then when I look at Stripe dashboard there are charges starting with ch_ and payments with py_

[hasty perch]

It's how they're represented under the hood

Functionally you can think of them the same

You'd use the charge api endpoints to interact with both: https://stripe.com/docs/api/charges

[hardy copper]

that is a bit confusing, is there a historical reasons why they are different

[hasty perch]

Yeah there is and it's a long one

And I can't reveal all

Just treat them the same essentially

[hardy copper]

ok thanks

feel free to close this thread

ty