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
- a373f7e49d3139ac6a12445641467749ec98b775ee29a3ad957a30c6d7c66915
- request
- 188c07daddb751e9b002b0070235e3916656aef4eb02c5752082067e479f4306
- transaction
- dd650b18866206448c2d85872ccc32914eb21e056e4c3d488eeb5ea0ced2a9b5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75125
the chainentry 75125
- sealed to the entry before
- 4e477e8af55f890adb620ec417a9dff438995b32f18606dfe78a543f925d9916
- this leaf
- 5c20c45f2364990b83a9629c84ac4d9f94e8ca0c0cb063e60c4ea72d043a17ce
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gFQQbKIDQp1Jox1jSdH75F+lxrRDCfct7PrE0NIOtV/XQJH6UXEFoa3n3yHlw3IRPQd/UxLOMEYPbtCBvytWBw==