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
- de916b545c1312df12864f3e72998dc7cd8dc2cc757351c74a51e4f83d3c7221
- request
- a042e8a5f962dc5b33491acb65225bd6a8bced3e99fc9f8259be525702de4447
- transaction
- 3becde868dc448e81ba026b7cefdcecd4bb2483046b7921075bf313aad6a1977computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41776
the chainentry 41776
- sealed to the entry before
- 3c446f0a452ef02acaef2d7ba120fdc7298c1ddcae279dffb5c1021ddd989419
- this leaf
- 8016c8532f6c559a8c35e175c2f122198f37a55d004819996471d3d18e04d449
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Aiz2u744vAvx00abR1YIOJYLj83/SytENH34DhaaTD2m+sPgju73sjj6d7ydYOEeyy1vzit20+xHQcCdBYLeAA==