Notifications

overview forter enables merchants to receive updates when a card, the underlying card of a token, or a network token is updated these notifications include relevant properties of the card excluding any pci data setup to enable notifications, forter requires two things an endpoint to which the notifications will be sent an hmac signing key, which allows the merchant to verify that the request originated from forter alternatively, forter can generate the signing key on your behalf and share it securely please provide the necessary details to your implementation engineer, and forter will ensure proper configuration update scenarios the following events will trigger a notification a card or the underlying card of a token is updated a network token or its underlying card is updated a card or token is updated via batch account updater this scenario is optional, as it may result in a large volume of updates please speak with your implementation manager to enable it example payload { "card" { "bin" "411111", "lastfourdigits" "1111", "expirationmonth" 12, "expirationyear" 2028 }, "networktoken" { "token" "2222850249903093", "state" "active", "expirationmonth" 12, "expirationyear" 2028, "paymentaccountreference" "5001ckvaxg3bf45lg87f63jvx3aq0" }, "updatesource" "au", // "au" or "nt" "changedfields" { "bin" "411111" } }