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 PIX charges, specifically allowing you to update existing PIX charge records. It is useful in financial automation workflows where you need to modify details of a PIX charge after its creation, such as updating payment information or correcting data.
Practical examples include:
- Adjusting the amount or description of a PIX charge.
- Changing metadata or custom fields associated with a PIX charge.
- Updating status or expiration details before the charge is paid.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the PIX charge to update. |
| Request Body | JSON object containing the fields and values to update on the PIX charge. |
| Additional Fields | Optional JSON object for any extra fields to include in the request (not mandatory here). |
Output
The node outputs the updated PIX charge data as a JSON object in the json output field. This typically includes all the updated properties of the PIX charge as returned by the Kobana API after the update operation.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Kobana API.
- The node dynamically selects the API base URL depending on whether the environment is production or sandbox.
- No other external dependencies are required.
Troubleshooting
- Invalid ID: If the provided PIX charge ID does not exist or is malformed, the API will return an error. Verify the ID correctness.
- Malformed JSON in Request Body: The "Request Body" must be valid JSON. Invalid JSON syntax will cause parsing errors.
- Authentication Errors: Ensure that the API key credential is correctly configured and has permissions to update PIX charges.
- API Environment Mismatch: Using production credentials against the sandbox URL or vice versa may cause unexpected errors.
- Missing Required Fields: The API might require certain fields in the update body; check the Kobana API documentation for required update parameters.
Links and References
- Kobana API Documentation (general reference for API endpoints and payloads)
- PIX Payment System (Brazilian instant payment system overview)
