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
- 156f6513c3dbc022843faf35acd858dca89547ebde9a23a1dfef6344d9fa3921
- request
- 13e1789b3da9dc20d2230f77560b9da64d145483386560d197437bc21a0e08f1
- transaction
- c3ccd1f74dbfe6a3883cde985295f01a04a07b12555fa4ffb65ce08b3d41a830computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61086
the chainentry 61086
- sealed to the entry before
- 5fe96816d17f274db278cd0974bc8272e0d5c1a62712ea759b49d6e339bc19a0
- this leaf
- 98bababbf9c50746526fe53f2c8f5e13cde11bf1c5b54ffffe72996e0395806d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DVBnQlyJFSYhGMhJ4fCim2YvCP6jY6TrgUX6eguOpTGOoVF1nxvxAdP6kUaZf9o3CcV2f7at0fo2KBbOjs5VBg==