paddle-billing-history

To display authenticated user billing history in Next.js, this skill retrieves customer transaction data from the Paddle API, handling server-side customer ID lookups to ensure strict data isolation. It formats transactions with locale-aware currency conversion for global markets.

Paddle API currency conversion for zero-decimal currencies like JPY and KRW involves formatting lowest-unit integers into locale-aware strings. This skill automatically handles these special cases alongside standard currencies to ensure accurate global transaction displays.

Yes, a mirrored customer database is required to fetch Paddle transaction history securely. This integration ensures data isolation by performing a server-side customer ID lookup, scoping the retrieved transaction data strictly to the authenticated user.

The best way to implement cursor-based pagination for Paddle transactions is using this skill's built-in logic, which manages API pagination requests and status filtering. It allows users to seamlessly browse past invoices and check payment statuses.

Yes, you can filter Paddle billing history by transaction status in your customer dashboard. This skill supports status filtering natively, allowing users to view specific past invoices, check payment statuses, and download receipts.

Paddle billing history supports downloading receipts without leaving your web application by retrieving and formatting transaction data directly from the Paddle API. This allows users to manage past invoices and receipts entirely within your customer dashboard.