# Events
## **KYC events**
| | | | |
| --------------- | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| **KYC Status** | **Events** | **Description** | **Occurance** |
| IN\_PROGRESS | user\_kyc\_in\_progress | User's KYC is in progress. | Queued for running KYC after ‘initiate KYC’ API is called |
| VERIFIED | user\_kyc\_verified | User’s KYC is complete and user details are verified. | User KYC is successfully complete. |
| RETRY | user\_kyc\_retry | If user KYC is not complete and additional details have to be provided. Once the details have been collected, ‘Initiate KYC’ API needs to be called again. | After the ‘initiate KYC’ API is called and user status is not VERIFIED. |
| SUSPENDED | user\_kyc\_suspended | When a user's KYC is rejected during KYC process. | |
| REVIEW\_PENDING | user\_kyc\_review\_pending | When a user’s KYC process is in review state. |
|
## **Transaction events**
| **Transaction Status** | **Event** | **Description** |
| ---------------------- | ----------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| INITIATED | No Webhook | The transaction request has been submitted in our system. |
| PENDING | transaction\_created | The transaction is undergoing compliance check or has been selected for processing. |
| PROCESSING | transaction\_processing | The transaction is being processed. |
| PROCESSED | transaction\_processed | The transaction has been processed successfully. |
| FAILED | transaction\_failed | The transaction was unable to be processed. |
| HOLD | transaction\_onhold | When the user’s transaction is on hold. The hold reason is provided in the response when fetching transaction information. |
| CANCELED | transaction\_canceled | The transaction was cancelled by the user or admin. |
| RETURNED | transaction\_returned | Transaction has been returned. |
| REFUNDED | transaction\_refunded | Transaction has been successfully refunded to the sender. |
## **Delivery events**
| **Delivery Status** | **Event** | **Description** |
| ----------------------- | ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| NONE | No webhook | Initial status. Transaction delivery has not been requested or transaction has not been forwarded for delivery. |
| PENDING | transaction\_delivery\_pending | Transaction has been forwarded for delivery. |
| DELIVERY\_REQUESTED | transaction\_delivery\_requested | Client has requested delivery of the transaction. |
| HOLD | transaction\_delivery\_onhold | Delivery of transaction has been placed on hold. |
| DELIVERY\_FAILED | transaction\_delivery\_failed | Transaction could not be delivered. |
| DELIVERY\_PAYOUT\_READY | transaction\_delivery\_payout\_ready | Only relevant for cash pick up transactions. Recipients can go pick up cash from the designated location when it is delivery payout ready. |
| DELIVERED | transaction\_delivered | Transaction has been successfully delivered/paid out to the recipient. |
| DELIVERY\_AUTHORIZED | transaction\_delivery\_authorized | Transaction delivery is authorized. If you are paying out transactions yourself as per agreement with Machnet, you can now proceed to delivery the transaction to the recipient. |
| DELIVERY\_CANCELED | transaction\_delivery\_canceled | When transaction is cancelled, transaction delivery is automatically cancelled too. |
## **Funding account events**
| **Event** | **Description** |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| user\_card\_added | User’s card account has been successfully added. |
| user\_card\_removed | User’s card account has been successfully removed. |
| user\_bank\_verification\_pending | User’s bank account has been added but verification status is “PENDING”. User can create a transaction using the funding account but it will not be processed until the account is verified. |
| user\_bank\_added | User’s bank account has been successfully added and the account has been verified. |
| user\_bank\_removed | User’s bank account has been successfully removed either through the widget or using API. |
| user\_bank\_verification\_failed | User's bank account verification failed and it is locked. User cannot use this bank account to create a transaction. |
| bank\_login\_required | User needs to re-login to their account. You will have to open the bank widget again with the particular funding account ID and ask user to login to their bank again. |
## **Widget events**
| Event | Description |
| ----------- | ---------------------------------------------------------------- |
| BANK\_ERROR | Error while adding bank using widget. Please try again. |
| CARD\_ERROR | Error while adding card using widget. Please try again. |
| BANK\_ADDED | Bank successfully added but account verification may be pending. |
## **CIP tag status events**
| Event | Description |
| ------------------- | ------------------------------------------------------------------------------------------------------ |
| cip\_tag\_submitted | User information has been successfully submitted. |
| cip\_tag\_reviewing | User information is under review. The status of this CIP tag will be updated once review is completed. |
| cip\_tag\_verified | User information has been successfully verified |
| cip\_tag\_failed | User information verification has failed |
| cip\_tag\_requested | User information has been requested. Please ask the user to submit this information. |