Get one payment
Retrieve one payment by the id Stripe gave its invoice.
This endpoint also answers QUERY, with the same parameters sent in the request body. How QUERY works.
Path parameters
Sent as JSON. Anything not listed here is ignored.
The id of the invoice at Stripe.
Returns
A payment object. Another account's payment answers 404, the same as one that does not exist.
The payment.
Always payment. It names the kind of record, so a caller holding several kinds can tell them apart without looking at where they came from.
The id of this record, as a string even when it reads as a number. It is what every endpoint naming this record takes.
Everything the record holds.
The id of the invoice at Stripe, which is also this record's id. It is what makes a confirmation Stripe sends twice recognisable as one payment.
Which plan was paid for: monthly, yearly or lifetime. It is kept as it stood on the day, so retagging a price at Stripe never rewrites the history, and it is null when the catalogue no longer knows the price that was charged.
The state of the invoice, as Stripe names it.
What was paid, in the smallest unit of the currency, tax included.
The tax share of that total, worked out by Stripe from where the buyer was, and already part of it rather than added to it.
The currency of both amounts, three letters as Stripe writes them.
The number Stripe gave the invoice, null when it gave none.
The page at Stripe where the invoice is read. Null when Stripe issued none.
The same invoice as a file. Null when Stripe issued none.
When Stripe finalised the invoice, as a count of seconds since 1970. It is what the list is ordered by.
Where to find this record.
The absolute address this record is read from.
Rate limit
Sixty requests per minute, per user, shared by every key and device. Every answer carries the budget left in X-RateLimit-Remaining.
Keys act as you, with exactly the access you have. Make one per integration so you can revoke it alone.