why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 285cda8e4f93535f8cd23ea3fdf13a4d13e344b87a451426f907be3e66dd81fc
- request
- 29b657ed0d11c7cc70f7fde3e2411a45fbe903061a300f42656ff0a9a84c4c36
- transaction
- 4b9c26108d199eb12d20f601067b28dd4222b71a7eff9a358f51eb6e08bd088ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12973
the chainentry 12973
- sealed to the entry before
- 97ac40791d28434edc2bbd5da46ebb934b0a7f8daa658aac61f808f005ab39de
- this leaf
- bc7e33a10f3670373b04dae658501846763f1ed7d7649974f84b060558e97344
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D+lgbuiYQYbKsnXkNgwwqWGRX34osACw2O0tqm9pHGXWcmEDgWQA44eMQNBzVZFP6wxb2be51VrB5Wzr4pHTAQ==