Use this endpoint to retrieve a paginated list of transactions across your accounts. It supports filtering by account number, date range, status, transaction type, and more — making it the primary endpoint for building transaction history views and automating reconciliation workflows.
Endpoint POST https://baasapi.payrepmfb.com/api/v1/transaction/api/fetch_transactions
Authentication: Bearer token. Pass your JWT in the Authorization header as Bearer <access_token>. Obtain a token via Generate Token .Request All filter fields are nested under a filters object. Pagination is controlled by top-level page and page_size parameters.
Body Parameters Optional object containing filter criteria for the transaction query. Filter transactions by a specific account number (10-digit).
Return only transactions on or after this date. Format: YYYY-MM-DD.
Return only transactions on or before this date. Format: YYYY-MM-DD.
Filter to a single calendar day. Format: YYYY-MM-DD. Takes precedence over start_date/end_date when provided.
Filter by transaction status. Common values: success, pending, failed.
Filter by transaction direction. Use credit for inbound payments or debit for outbound transfers.
Filter by transaction category (e.g., collection, transfer).
Fetch a specific transaction by its unique reference number.
Filter by the payment channel used (e.g., nip, intra).
Free-text search across transaction fields such as narration and reference number.
Page number for paginated results. Starts at 1.
Number of transactions to return per page. Minimum 1.
Maximum number of results to return. Minimum 1.
Cursor for cursor-based pagination. Pass the created_at timestamp of the last item from the previous page.
Cursor ID paired with cursor_created_at for stable cursor-based pagination.
Response A successful response returns the standard envelope with a paginated array of transaction objects in data.
Response Fields true when the request succeeded.
"00" on success. See the error table below for other codes.
Human-readable status message.
Array of transaction objects matching your filters. Unique identifier for the transaction. Use this for reconciliation and status lookups.
The account number associated with this transaction.
The name of the account associated with this transaction.
Transaction amount in the base currency (e.g., "5000.00").
Direction of the transaction: credit (inbound) or debit (outbound).
Category of the transaction, such as collection or transfer.
Current status of the transaction: success, pending, or failed.
Payment channel used, e.g., nip (interbank) or intra (intra-bank).
Narration or description attached to the transaction.
ISO 8601 timestamp of when the transaction was recorded.
Example Request curl --request POST \ --url https://baasapi.payrepmfb.com/api/v1/transaction/api/fetch_transactions \ --header 'Authorization: Bearer <access_token>' \ --header 'Content-Type: application/json' \ --data '{ "filters": { "account_number": "7801234567", "start_date": "2026-04-01", "end_date": "2026-04-28", "transaction_type": "credit", "status": "success" }, "page": 1, "page_size": 20 }'
Response { "status" : true , "response_code" : "00" , "message" : "Transactions fetched successfully" , "data" : [ { "reference_number" : "TXN-20260415-00123" , "account_number" : "7801234567" , "account_name" : "Lagos Branch Sales" , "amount" : "50000.00" , "transaction_type" : "credit" , "transaction_category" : "collection" , "status" : "success" , "channel" : "nip" , "remarks" : "Payment for Invoice #INV-0042" , "created_at" : "2026-04-15T10:32:00Z" } ] }
Error Codes Response Code Meaning 00Success 41Customer not found — invalid API credentials 60Customer not active
