#gee

1 messages · Page 1 of 1 (latest)

narrow pivotBOT
hasty beacon
#

Which dashboard accessible/page are you referring to?

icy sleet
#

/payments/ch_xxxx

hasty beacon
#

We don't have an API for the payment timeline. You may keep track of the Webhook events of a Payment Intent (payment_intent.*) or Charge (charge.*). They should be able to build your own timeline based on those events

icy sleet
#

in the charge search api for this particular charge the payment intent comes out as null

hasty beacon
#

Could you share the request ID (req_xxx) of this search query, its response and the payment intent (pi_xxx) that you expected it to be non-null?

icy sleet
#

requestid:req_x1ZdBs3KjSqoTX

#

not sure how to find the expected payment intent

#

trying to see how i can get the timeline

#

shouldnt there be a paymentintent associated with every charge?

hasty beacon
#

Payment Intent ID will only be available if you use Payment Intent API. ch_1Hm79oE75wsYtv8YGN8zcWc9 was made with Charges API, so Payment Intent ID will not be available

icy sleet
#

oh..

#

ok

hasty beacon
icy sleet
#

you mean all charges api (search,retrieval etc)are not recommended?

hasty beacon
#

Yup! Charges API in general: https://stripe.com/docs/payments/charges-api

The content of this section refers to a Legacy feature. Use the PaymentIntents API instead.

The Charges API doesn’t support the following features, many of which are required for credit card compliance:

  • Merchants in India
  • Bank requests for card authentication
  • Strong Customer Authentication
icy sleet
#

ok. am not using api to create charges.

#

just doing search for payments using api

hasty beacon
#

How are your payments created now then? You have to create the payments via Charges API or Payment Intents API in order to perform a search

#

If you use Charge API to create a payment such as ch_1Hm79oE75wsYtv8YGN8zcWc9, Payment Intent won't be available