Webhooks provide real-time notifications for API events, enabling your platform to receive timely updates about specific activities. Our system sends these notifications to a designated endpoint within your hosted environment, which is configured to adeptly receive and process them.

Leverage webhooks to promptly obtain information about critical API events. These events include occurrences external to your system, such as a new deposit in an MPC wallet or a card transaction at a point-of-sale (POS) terminal.To seamlessly receive and process webhook-enabled events, you need to establish and configure a webhook endpoint within your environment.

Each webhook request consists of a common part and a custom payload specific to the event being communicated. The common part includes standard information such as the event type, sub-type, status and a unique Id of of the notification, while the custom payload contains detailed data relevant to the specific event.

General payload example:

 
{
  "operation": "TREASURY",
  "sub_operation": "DEPOSIT",
  "operation_id": "ca0c57d2-b1c9-4bcd-9d5d-8d361cad6fddds1c",
  "status": "FINISHED",
  "data": { }
}

This endpoint allows you to generate a new number, CVV and expiry date for a given card.

When a card with a givencardID is lost, damaged or suspected of fraudulent use, this endpoint will generate a new number, CVV and expiry date for your card with the same cardID.

If the card was previously tokenized and provisioned to a mobile wallet (e.g. Google Pay), the newly created card should remain linked to the mobile wallet. However, for subscription-based services, the cardholder may need to re-enter the new card details and verify the card again. While the 16-digit Number, CVV, and expiry date will change, the cardIdremains the same as well the balance, movements and other information will remain unchanged.

Required access level: Admin Access (Level 3)