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
- a578ccc9a92f4b312d34016ec8ec17463dfdcb12b68a747a86645d79a78d1226
- request
- d3cbb3fb4d8d712ab95bb45a93fea6e54556d4eccfb4f141bebd3ca8ea612cd3
- transaction
- d0ead89e1ae0e887682da004042342cdee2babfa38cc0d8682d66d8b3e21e8a7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46292
the chainentry 46292
- sealed to the entry before
- 1e807a3e67d816999bbed57d3f3fe2aff006ab2fbf52871c5c0fa50a0db72c9b
- this leaf
- 6e6ea5d7fe9ad2f24f35590d31ae21e28a9127d4c6f3cb3963a8463506390900
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bvQJYavhIvOm3J/JF2HKCVbnQatVYJVZTO+RTQNslEqbbyjGjYXRm6PlH/k3YrGUIoDih+0mCVcZKTH7gCh6DA==