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
- a228504cc14d7545196ec30e7b6f03f90e8b4ec32aa18d85416e5b21c64c3170
- request
- 7113dc919cf64b77acbaa3ba6c3dc45c8b1324173c338c0279a5efd16431fbec
- transaction
- 2f0bc22cda58dbc6d94b10aaeb7084792c0f20cc56e8070584f0e29706e015d8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31979
the chainentry 31979
- sealed to the entry before
- 1841000b5eab370a479efdc17fa2478eb3b2ecfb5007525f3645c9515071022e
- this leaf
- 7bc468923715ed50c4f6ec535c8e1397b11aee58c9e7b18fd3c52632988d79cd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HH0O4hokWw9V7eX3YW6cgDy2mTusnh4OVYH8zmc953Ll6eTBsMo7Ip8SXhhmYZ+M7t80qpQ9t6lb2kglL/qhDQ==