Billing receipts via Paddle API (#4 remainder) #9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/receipts"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Completes #4 now that
PADDLE_API_KEYis provisioned on the VPS.paddleAPIclient fromPADDLE_API_KEY+PADDLE_API_URL(sandbox now; live = swap both at launch). Nil key = billing endpoints answer 503, everything else unaffected.GET /v1/receipts: the org's Paddle transactions (via the customer ids recorded on its license records), newest first — date, total (minor units), currency, status, invoice number. Members can view (per the #6 role model).GET /v1/receipts/{id}/invoice: short-lived invoice-PDF URL, authorized by checking the transaction's customer id against the org's records — foreign transactions are indistinguishable from not-found.Tests against a fake Paddle server: listing (auth header verified), owned-invoice passthrough, foreign-invoice 404, unauthenticated 401, unconfigured 503. Green on the runner.