Zendry Global API 1.0 icon

Zendry Global API 1.0

Acesso universal à API Zendry (Pix, Payments, Webhooks, Account, Crypto, Checkout) via AccessToken

Actions120

Checkout → Simulate QRCode Payment

AI-generated

Overview

This node interacts with the Zendry API to perform various operations related to the Checkout resource, specifically simulating QRCode payments. It allows users to simulate a payment on a QRCode by sending a POST request to the Zendry API with the required reference ID and optional additional parameters. This is useful for testing payment flows or simulating transactions in a development or staging environment.

Use Case Examples

  1. Simulate a QRCode payment by providing the reference ID of the QRCode and optional parameters such as authorization status or external references.
  2. Use the node to test webhook notifications triggered by simulated payments.
  3. Integrate with Zendry's payment system to automate payment simulations as part of a larger workflow.

Properties

Name Meaning
Access Token A valid Bearer access token for authenticating with the Zendry API.
Base URL The base URL of the Zendry API, defaulting to https://api.zendry.com.br, which should not be changed unless necessary.
Additional Fields Optional parameters that can be added to the request, such as generator name, document, external reference, expiration time, external link, filters, webhook URL and type, authorization header for webhook, and payment authorization status.
Required Fields (JSON) JSON object containing the required fields for the operation as per the Zendry API documentation.

Output

JSON

  • json - The JSON response from the Zendry API after simulating the QRCode payment, containing details of the simulated payment or error information.

Dependencies

  • Zendry API

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to perform the simulate QRCode payment operation.
  • Verify that the reference_id is provided either in the requestBody JSON or additionalFields; it is mandatory for this operation.
  • Check that the requestBody JSON is valid and correctly formatted to avoid JSON parsing errors.
  • If the API returns an error, review the error message for details such as invalid parameters or authorization issues.
  • Make sure the Base URL is correct and reachable from the environment where the node is running.

Discussion