Webhooks Flow

This sections describes the webhooks that you will receive in the operations related to SPEI IN and SPEI OUT

Success SPEI IN

This flow occurs when a successful transaction is received from SPEI to a CLABE account. Once you register your endpoint for our webhook, you will get a request every time a SPEI IN arrives.

Related Events

  1. SPEI_WEBHOOK_ACCEPTED

Refunded SPEI IN

Tehre will be some times were you accept a money in, but for any reason, you have to refund it. You can do it with the Refund Endpoint. This flow occurs when a successful transaction is received from SPEI to a CLABE account and you request a refund of the transaction.

This refund action generates an extra transaction (SPEI OUT type) to return the money to original payer. Thats why a success CashOut event is triggered.

Related Events

  1. SPEI_WEBHOOK_ACCEPTED
  2. Refund Endpoint
  3. SPEI_WEBHOOK_REFUNDED
  4. SPEI_ACCOUNT_CASH_OUT_SUCCESS

Success SPEI OUT

This flow occurs when a SPEI cashout is requested and successful. In this case, the cashout endpoint generates the pending cashout request, and we notify the transaction's success via a webhook notification. In the event that it can be executed immediately, a pending status is not generated; success is returned immediately.

Related Events

  1. SPEI_ACCOUNT_CASH_OUT_CREATED
  2. SPEI_ACCOUNT_CASH_OUT_SUCCESS

REFUNDED SPEI OUT

This flow happens when for some special issue a success cashout transaction must be refunded. After a succes webhook notification you will receive a failed cashout notification.


Related Events

  1. SPEI_ACCOUNT_CASH_OUT_CREATED
  2. SPEI_ACCOUNT_CASH_OUT_SUCCESS
  3. SPEI_ACCOUNT_CASH_OUT_FAILED

Failed SPEI OUT

There are some cases outside our organization and system in which a SPEI OUT transaction cannot be executed. In these cases, we can return three types of events: cancelled, rejected, or declined. In any of these three cases, it indicates that the transaction was not executed.