Modulr cards webhooks:

Modulr cards integration also includes webhook notifications that allow receiving more information about a card's events, such as transactions, status updates, etc.

This way we can synchronise information with Modulr as BaaS without having to ask each time we do an operation on their side.

During the integration of the Modulr card, we configured the following notifications to be received by email by the Admin user, and also for Directors and Account Owners.

Customer creation

We implemented the CARD_AUTH webhooks notifications which inform when a new client was created under a Modulr customer on our side so that it shows as a new customer on Modulr's side.

Cards webhooks

We have also implemented 3 types of webhook notifications related to cards:

CARDAUTH

It will be saved in logs, but it will not be configured as a webhook transaction
- Approved card Authorisation.
- Declined card Authorisation (Reason field will specify the decline reason).
- Subsequent Decline of previously Approved Authorisation (this happens in case of a network outage. Reason field will include Timeout information and PreviousActivityStatus will specify "APPROVED").
- Authorisation Reversal (when the transaction is partially or fully reversed, OrderID can be used to link any reversed amount with a previously approved Authorisation).
- Use of PAYIN and PAYOUT to identify any card payment from a CardID or refund linked to a specific AccountID.
- To check transactions coming from different cards associated with a specific Account, search for the PaymentID field containing the card activity BID, which you can use to query additional details from the card activities API. We will also use the OrderID to match the settlement to the authorisation record as part of their internal reconciliation.
- The relation between order and status will be:
  - 8, 11 and 20: FAILED. The scenario of the order in Modulr will be our failure Reason
  - 12 and 13: PENDING
  - 19, 21 and 22: ACCEPTED
  - See related documentation here

CARDCREATION

This sends a webhook notification that informs the outcome of a successfully submitted 'Create physical card' request. Possible results are:
- Error: the Admin user or Director will receive an email if the card was not created.
- Created: the Admin user or Director will receive an email when a new card was created successfully.
This is only supported for Physical Cards.
Webhooks will be retried in case of failure.

CARDSTATUSUPDATE

Admin users or Directors will receive an email notification in the following cases:
- CREATED (just for Physical cards)
- ACTIVE (Just for Physical cards)
- BLOCK
- UNBLOCK
- CANCEL
- EXPIRED
- SUSPENDED
This sends a webhook notification in the event of a card changing status, regardless of what triggered/performed the status update. This can help customers be informed of card status changes that were not initiated by their API user e.g. card status change performed via the Customer Portal, or a card status initiated by an internal Modulr process e.g. card expiry.

Modulr documentation related