Documentation Index
Fetch the complete documentation index at: https://docs.propaga.mx/llms.txt
Use this file to discover all available pages before exploring further.
Webhook Endpoint
You should configure your webhook endpoint to receive POST requests from Propaga. The webhook will send the transaction confirmation data in JSON format. Please contact us to set up the webhook.Payload Structure
Here’s an example of the webhook payload you’ll receive:Payload Fields
| Field | Type | Description |
|---|---|---|
transactionId | String | The Propaga’s ID of the transaction. |
cornerStoreId | String | The ID of the corner store. |
wholesalerTransactionId | String | The ID of the transaction in the wholesaler system. |
totalAmount | Number | The total amount of the transaction. |
interest | Number | The interest of the transaction. |
totalAmountWithInterest | Number | The total amount of the transaction with interest. |
movementDate | String | The date when the transaction was moved to on-hold. |
status | String | The status of the transaction. |
Handling the Webhook
Here’s an example of how to handle the webhook in different programming languages:Best Practices
- Verify the Webhook Source: Implement security measures to verify that the webhook is coming from Propaga.
-
Implement Idempotency: Store the
referenceNumberto avoid processing the same conciliation multiple times. - Handle Errors Gracefully: Implement proper error handling and logging to track any issues with webhook processing.
- Respond Quickly: Your webhook endpoint should respond as quickly as possible. If processing takes time, handle it asynchronously.
- Validate Data: Always validate the incoming data before processing it.

