> ## Documentation Index > Fetch the complete documentation index at: https://docs.payaza.africa/llms.txt > Use this file to discover all available pages before exploring further. # Fetch Payment Link Transactions > It retrieves the list of transactions for a specific payment link. ## OpenAPI ````yaml /openapi.json get /payment-link/merchant/fetch-payment-link-transactions?link_id=41268&page=1 openapi: 3.0.1 info: title: Payaza Documentation version: 2.0.0 description: >- API reference for processing payments using Card, Bank Transfer, USSD, and QR Code methods. servers: - url: https://api.payaza.africa/live security: - ApiKeyAuth: [] - TenantID: [] - ProductID: [] tags: - name: Transfers description: >- Transfers are transactions made from your Payaza account to beneficiaries. Merchants can instantly transfer funds from their available balance. For every transfer, you need to specify the amount and the beneficiary’s details. You become eligible to make transfers after you have been verified. (you sign up, finish account activation and KYC verification). - name: Payaza Account description: >- This is our internal account that can be used to make payouts to other bank accounts, in single or in bulk. The Payaza account can also be used to receive settlements. It can also be used to track the transfer status of your transactions and check your balance instantly - name: Sub Accounts description: >- This enables you to establish Sub Payaza accounts for your customers. Each sub-account comes with an assigned static virtual account, facilitating direct funding for individual accounts. Furthermore, the Main Payaza account can directly initiate funding for each sub-account. These sub-accounts serve the purpose of managing unique account positions or balances and facilitating disbursements from these positions to specified beneficiaries. - name: EUR Accounts description: >- This endpoints enable you to create EUR subaccounts which can be used to make transfers as required . - name: Apple Pay and Google Pay description: >- Apple Pay and Google Pay give your customers a fast, familiar, and secure way to complete payments. Our APIs provide a gateway to provide these services to your users for a smooth payment experience. - name: Virtual Accounts description: >- Virtual Accounts are bank accounts that are created for a specific purpose and last for specified durations. Virtual accounts are issued by Payaza’s partner banks. Our virtual account APIs can be used to create virtual accounts and perform other tasks relevant to virtual accounts. Virtual accounts are created to foster easy payment collections for your business and platform. Static/Reserved Account: This virtual account is created by the merchant and remains valid indefinitely. It can be used multiple times and does not expire. Dynamic Account: This virtual account is generated for a specific transaction or purpose. Please note that dynamic virtual account remains valid for a temporary period of time or until a payment of the specified amount is received. Upon expiry, a merchant can generate another one for a different purpose. - name: Card Collection description: >- The Card Collection APIs can be used to make card transactions, refund transactions that have been performed, check the status of a transaction and so much more. - name: Card Tokenisation description: >- The Card Tokenisation APIs are used to create card tokens, charge cards using tokens, retrieve all tokens created by a merchant account and deleting any card token as desired. - name: Refunds And Chargebacks description: >- The Refunds and Chargeback APIs are used to initiate refunds, view your refund and chargeback history and so much more. - name: Branches description: >- The Refunds and Chargeback APIs are used to initiate refunds, view your refund and chargeback history and so much more. - name: Auth-Capture-Void description: >- The Auth-Capture-Void APIs provide a two-phase payment process where transactions are first authorized, then captured or voided. This allows merchants to hold funds and complete the transaction in the future. - name: Momo and ZAR Collections description: APIs for MoMo, ZAR and XOF collections. - name: Check Transaction Status(Merchant Reference) description: >- This endpoint is used to check the transaction status of a transaction using the Merchant Reference.. paths: /payment-link/merchant/fetch-payment-link-transactions?link_id=41268&page=1: get: tags: - Payment Links summary: Fetch Payment Link Transactions description: It retrieves the list of transactions for a specific payment link. parameters: - name: link_id in: query required: true schema: type: integer default: '41268' description: The ID of the payment link for which to fetch transactions. - name: page in: query required: true schema: type: integer default: '2' description: The page number to be retrieved. responses: '200': description: Request Successful content: application/json: schema: $ref: '#/components/schemas/fetchPaymentLinkTransactionsResponse' examples: Fetch Payment Link Transactions: summary: Fetch Payment Link Transactions value: status: true message: Payment Link Transactions fetched successfully data: items: - transaction_id: 90123451 transaction_payable_amount: 15000 transaction_amount: 15000 transaction_fee_amount: 250 transaction_start_date: '2026-09-25T10:15:30.123456' transaction_status: Completed currency_name: Naira transaction_reference: P-C-20260925-ABCDEF123 transaction_channel: Checkout transaction_mode: Card customer_pay_fee: false customer_response: email_address: customer1@example.com - transaction_id: 90123452 transaction_payable_amount: 5500 transaction_amount: 5500 transaction_fee_amount: 100 transaction_start_date: '2026-09-24T14:45:12.654321' transaction_status: Failed currency_name: Naira transaction_reference: P-C-20260924-XYZ987UIO transaction_channel: Checkout transaction_mode: VirtualAccount customer_pay_fee: false customer_response: email_address: johndoe@example.com - transaction_id: 90123453 transaction_payable_amount: 3200.5 transaction_amount: 3200.5 transaction_fee_amount: 50.5 transaction_start_date: '2026-09-23T08:20:05.987654' transaction_status: Initialized currency_name: Naira transaction_reference: P-C-20260923-LMN456QWE transaction_channel: Checkout transaction_mode: Unknown customer_pay_fee: true customer_response: email_address: janedoe@example.com pagination: total: 3 per_page: 10 current_page: 1 total_pages: 1 '400': description: Invalid request security: - ApiKeyAuth: - Payaza {{Public API Key In Base64}} components: schemas: fetchPaymentLinkTransactionsResponse: title: Fetch Payment Link Transactions Response type: object properties: status: type: boolean description: Indicates whether the request was successful. example: true message: type: string description: A descriptive message regarding the outcome of the operation. example: Payment Link Transactions fetched successfully data: type: object description: >- The payload containing the list of transactions and pagination details. properties: items: type: array description: >- An array of transaction records associated with the payment link. items: type: object properties: transaction_id: type: integer description: The internal unique identifier for the transaction. example: 70113301 transaction_payable_amount: type: number description: The total amount payable by the customer. example: 100 transaction_amount: type: number description: The base transaction amount. example: 100 transaction_fee_amount: type: number description: The fee charged for processing the transaction. example: 50 transaction_start_date: type: string format: date-time description: The timestamp when the transaction was initiated. example: '2026-03-21T15:05:41.492641' transaction_status: type: string description: The current status of the transaction. example: Completed currency_name: type: string description: The name of the currency used for the transaction. example: Naira transaction_reference: type: string description: The unique reference string for the transaction. example: P-C-20260321-WET5K01FCI transaction_channel: type: string description: The channel through which the transaction was made. example: Checkout transaction_mode: type: string description: The payment method or mode used. example: Card customer_pay_fee: type: boolean description: Indicates whether the customer bore the transaction fee. example: false customer_response: type: object description: Details about the customer who made the payment. properties: email_address: type: string format: email description: The email address of the customer. example: johndoe@gmail.com pagination: type: object description: Metadata for navigating through pages of transaction records. properties: total: type: integer description: The total number of transactions available. example: 29 per_page: type: integer description: The number of transactions returned per page. example: 10 current_page: type: integer description: The current page number being returned. example: 1 total_pages: type: integer description: The total number of pages available. example: 3 securitySchemes: ApiKeyAuth: type: apiKey in: header name: Authorization description: Payaza {{Public API Key in Base 64}} TenantID: type: apiKey in: header name: X-TenantID description: live or test ProductID: type: apiKey in: header name: X-ProductID description: 'default value is ‟app” ' ````