#anhnh_api

1 messages ¡ Page 1 of 1 (latest)

past pathBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1357248036991926293

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

slow terrace
#

For Charges object, you can still use Charge Retrieval API to retrieve the information

dusk heath
#

How can I differentiate between these two types? Can I rely on the prefix ch_ for Charges and pi_ for PaymentIntents?

slow terrace
#

For Payment Intents, the prefix will be pi_. For Charges API, the prefix will be ch_ or py_

dusk heath
#

Yes, I just want to confirm, the migration to PaymentIntents should only be applied for creating payments, right? For other APIs, I can still use the Charge API, correct?

slow terrace
#

Payment Intents API should do the same thing as Charges API, i.e. creating and completing the payments. If you use Payment Intents API, you shouldn't need Charges API. Why are you going to use Charges API after migrating to Payment Intents API?

#

Charges API is legacy and shouldn't be used

dusk heath
#

In my case, I need to retrieve the payment history, and it's through the charge API. So, I need to use both APIs

slow terrace
#

If it's only for information retrieval, then using Charges API will be fine. For new payments, they should all be on Payment Intents.

dusk heath
#

Ok, I got it. thank you for support.