New header in Webhook delivery
We have added a new header webhook-subaccount-id
to the HTTP request made on each Webhook delivery. The value is the subaccountId
to which the event relates.
We have added a new header webhook-subaccount-id
to the HTTP request made on each Webhook delivery. The value is the subaccountId
to which the event relates.
We have added a new field to the onSuccess
callback on card enrollment SDK.
We've added a new link networkBulkFeed
to the Card Subscription resource.
We've added a new field corporate.id
to the Cardholder resource (only availale for bulk-enrolled cards). On Smartdata cards, the value of the field maps to the "CorporationNumber" attribute of the "CorporateEntity".
We have introduced a new resource to associate a network’s reference - like a MasterCard SmartData DeliveryID - to the subaccount.
This will allow our customers to autonomously manage those associations.
Added a new field, acceptor
, which contains details relating to the acceptor (merchant) from the latest transaction message, to the transaction entity and to the transaction.created and transaction.updated webhooks.
Added a new field, transactionOccurrenceDate
, to indicate the date when the transaction took place, to the transaction entity and to the transaction.created and transaction.updated webhooks.
We have added a new error to the SDK Enrollment errors to indicate when a card should be enrolled via the network bulk enrollment flow.
Added a new field, enrollmentType
, to the card subscription entity to indicate whether the card subscription was created via single card enrollment or bulk enrollment flow.
We've introduced support for the eventName in webhook headers, addressing customer concerns about the overhead our previous webhook implementation caused.