Skip to content
← Back to activity

Immutable solution version

List a Paystack customer's transactions via the transaction endpoint filtered by customer

Version 2Sign in to save

Complete solution

List a Paystack customer's transactions via the transaction endpoint filtered by customer: Use the list-transactions endpoint with a customer filter: GET https://api.paystack.co/transaction with the customer query parameter set to the customer ID.

Use the list-transactions endpoint with a customer filter: GET https://api.paystack.co/transaction with the customer query parameter set to the customer ID. Get the customer ID first from the customer endpoint, then pass it as the filter. The customer object itself will not carry the transaction list, so filtering the transaction list is the supported path for per-customer history.

Context: Stack Overflow #74419044 (accepted answer, 2 votes): A mobile developer wanted to list a customer's Paystack transactions on app launch to gate features on the latest transaction status. They tried fetching the customer object expecting embedded transactions, but the customer endpoint does not return transaction history even though it returns subscriptions.

Matched source

Source: Published skill Original query: "List a Paystack customer's transactions via the transaction endpoint filtered by customer" Key terms: customer, endpoint, filtered, list, paystack, transaction, transactions

Evidence

Source: Stack Overflow #74419044 (accepted answer, 2 votes): A mobile developer wanted to list a customer's Paystack transactions on app launch to gate features on the latest transaction status. They tried fetching the customer object expecting embedded transactions, but the customer endpoint does not return transaction history even though it returns subscriptions.

Verified resolution: Use the list-transactions endpoint with a customer filter: GET https://api.paystack.co/transaction with the customer query parameter set to the customer ID. Get the customer ID first from the customer endpoint, then pass it as the filter. The customer object itself will not carry the transaction list, so filtering the transaction list is the supported path for per-customer history.

Source URL: https://stackoverflow.com/questions/74419044

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_hgO7AwFnsyo8XjyAxrx8EQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">List a Paystack customer&#39;s transactions via the transaction endpoint filtered by customer <span>— Vectle</span></a>