Actions215
- V1 > Bank Billets Actions
- V1 > Bank Billet Accounts Actions
- V1 > Bank Billet Batches Actions
- V1 > Bank Billet Batch Exports Actions
- V1 > Bank Billet Discharges Actions
- V1 > Bank Billet Payments Actions
- V1 > Bank Billet Registrations Actions
- V1 > Bank Billet Remittances Actions
- V1 > Customers Actions
- V1 > Customer Subscriptions Actions
- V1 > Discharges Actions
- V1 > Email Deliveries Actions
- V1 > Events Actions
- V1 > Imports Actions
- V1 > Installments Actions
- V1 > Remittances Actions
- V1 > Reports Actions
- V1 > SMS Deliveries Actions
- V1 > User Info Actions
- V1 > Webhook Deliveries Actions
- V1 > Webhooks Actions
- Admin > Users Actions
- Admin > Connections Actions
- Admin > Certificates Actions
- Admin > Subaccounts Actions
- Charge > PIX Actions
- Charge > PIX Accounts Actions
- Data > Bank Billet Queries Actions
- EDI > EDI Boxes Actions
- Financial > Accounts Actions
- Financial > Balances Actions
- Financial > Commands Actions
- Financial > Statement Transactions Actions
- Financial > Transaction Imports Actions
- Financial > Providers Actions
- Payment > Bank Billets Actions
- Payment > Bank Billet Batches Actions
- Payment > Batches Actions
- Payment > DARFs Actions
- Payment > DARF Batches Actions
- Payment > PIX Actions
- Payment > PIX Batches Actions
- Payment > Utilities Actions
- Payment > Utility Batches Actions
- Transfer > Batches Actions
- Transfer > Internal Actions
- Transfer > Internal Batches Actions
- Transfer > PIX Actions
- Transfer > PIX Batches Actions
- Transfer > TED Actions
- Transfer > TED Batches Actions
Overview
This node integrates with the Kobana API to manage various financial and payment-related resources. Specifically, for the Payment > PIX resource with the Get operation, it retrieves detailed information about a specific PIX payment by its unique ID.
Use cases include:
- Fetching the status and details of a PIX payment transaction.
- Verifying payment information before processing further business logic.
- Auditing or reporting on individual PIX payments.
Example: You have a PIX payment ID from a previous workflow step and want to retrieve all associated data such as amount, payer info, and payment status.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the PIX payment to retrieve. This is required to specify which PIX payment record to fetch. |
Output
The node outputs a JSON object representing the PIX payment details returned by the Kobana API. This typically includes fields such as payment amount, date, status, payer information, and other metadata related to the PIX payment.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Kobana API via an API key credential.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- Proper permissions on the Kobana API are necessary to perform read operations on PIX payments.
Troubleshooting
Common issues:
- Invalid or missing PIX payment ID will cause the API request to fail.
- Network connectivity problems or incorrect API credentials can prevent successful API calls.
- Using the wrong environment setting (sandbox vs production) may lead to unexpected results or no data found.
Error messages:
"Resource not found"or similar indicates the provided ID does not exist.- Authentication errors suggest invalid or expired API credentials.
- JSON parsing errors may occur if input parameters are malformed.
Resolutions:
- Verify the PIX payment ID is correct and exists in the Kobana system.
- Check that the API key credential is valid and has appropriate access rights.
- Confirm the environment setting matches where the PIX payment was created (sandbox vs production).
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- PIX Payment Information (Central Bank of Brazil official PIX system overview)