#fitzlong_api
1 messages · Page 1 of 1 (latest)
👋 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/1430516778454351882
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- fitzlong_api, 37 minutes ago, 15 messages
- fitzlong_api, 2 hours ago, 9 messages
- fitzlong_api, 22 hours ago, 12 messages
I don't understand the question. What specifically are you trying to do?
This was the answer from your colleague before.
Right, but there's conflicting info there and to what you describe. What kind of payments are you doing (e.g. what mode do you set when you create a session?)?
Embedded form
That doesn't answer my question
What mode do you set when you create a session? payment? subscription?
sorry,it is payment
OK, then:
If I omit the invoice_creation.enabled parameter in the Checkout Session, does that mean I can only issue an invoice to my customer via “Pay an invoice”?
Yes, if you don't enable post-payment invoices via the parameter then you'd need to create an invoice after the fact
In that case, the “Create an invoice” API seems meaningless 🤔
Not sure what this means
"Since your colleague mentioned this document, I reviewed it and noticed that it indicates creating invoices via the pay API, which led to my confusion."
Well you first create the invoice, and then pay it separately. Neither is meaningless – you can't do both in a single step/with a single API
So for issuing invoices after payment, the correct sequence is to first create the invoice and then pay it, rather than, as previously mentioned, just using the pay API.
So if you want to create a paid invoice without using Checkout's built-in functionality, then yes you'd:
- Create the invoice via the create endpoint
- Pay it and mark it
paid_out_of_band
Yes
翻译成英文可以这样表达:
I have another question: what is the difference between Hosted Invoice Page and Checkout Embedded Form? Is it that the Hosted Invoice Page allows both invoicing and payment, while the Checkout Embedded Form only supports payment?
Well, Checkout does support invoicing as we explained previously. You need to enable it
The HIP is a hosted URL that allows customers to view and pay their invoices
i see, thk, have a nice day
No problem, glad I could help!