beth_69536

[lapis monolith]

hello! Can you give an example of what you mean by each of the payment status in Stripe connect?

[lapis monolith]

We don't have a detailed definition for each of those statuses unfortunately. The Dashboard provides a simplified view

To briefly summarize, you'll create a PaymentIntent that you can consider as the "intent to pay". When there is an attempt to pay, a Charge object is created.

You can view the descriptions of some of the PaymentIntent status here : https://stripe.com/docs/payments/paymentintents/lifecycle#intent-statuses

You can see things like disputes and refunds on the corresponding Charge object : https://stripe.com/docs/api/charges/object

[trail fern]

OK - can you please explain where an payment would be in the uncaptured or incomplete status?

would you advise we map to these status' in the dashboard or to the payment intents only??

[lapis monolith]

I think you should consider what you want to do with the Payment Statuses? i.e. what's the aim of mapping them?

uncaptured -> Stripe supports auth and capture : https://stripe.com/docs/payments/place-a-hold-on-a-payment-method. If the payment has been authorized but not yet captured, that's indicates the PaymentIntent currently uncaptured.

[trail fern]

we want to showcase a realtime view of the buyer payment status to our customers (ie the sellers)

Our status'

Unpaid
Pending
Authorised
Paid
Overdue

[lapis monolith]

are you using auth and capture?