Bayarcash icon

Bayarcash

Consume Bayarcash API

Transaction → Get Transaction by ID

AI-generated

Overview

This node interacts with the Bayarcash API to retrieve details of a specific transaction by its ID. It is useful in scenarios where you need to fetch transaction information such as status, amount, payer details, and other metadata for a given transaction identifier. For example, it can be used in financial workflows to verify payment status or to audit transaction records.

Use Case Examples

  1. Retrieve transaction details by providing the transaction ID (e.g., trx_z88ymJ) to monitor payment status or validate transaction data.
  2. Use in automated workflows to fetch transaction information for reporting or customer service purposes.

Properties

Name Meaning
Transaction ID The unique identifier of the transaction to retrieve (e.g., trx_z88ymJ). This is a required input to specify which transaction's details to fetch.

Output

JSON

  • id - The unique identifier of the transaction.
  • status - The current status of the transaction.
  • amount - The amount involved in the transaction.
  • payer_name - Name of the person who made the payment.
  • payer_email - Email address of the payer.
  • payment_channel - The payment channel used for the transaction.
  • created_at - Timestamp when the transaction was created.
  • updated_at - Timestamp when the transaction was last updated.

Dependencies

  • Bayarcash API with a valid API token credential

Troubleshooting

  • Authentication failed due to invalid or expired API token. Ensure the API token is correct and has not expired.
  • Validation errors if the transaction ID is missing or improperly formatted. Provide a valid transaction ID.
  • Bad request errors if the request parameters are incorrect or malformed.
  • Forbidden errors if the user does not have permission to access the transaction or if the payment channel is not enabled for the account.
  • Not found errors if the specified transaction ID does not exist.
  • Server errors if the Bayarcash API server encounters an issue. Retry after some time or contact support.

Links

Discussion