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
- 3f74ca12055061e114c98cbf7e040204617a47cccb063df3b3e3067a3cbe9314
- request
- d13ef7437dfb05f5e307f1848c0673253f354c4aa22292c6b2da507a4354ec61
- transaction
- 210ffe89a00882a5a8edf6e0082a38900695558a1aec3cfa101dbd7656c126e7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20721
the chainentry 20721
- sealed to the entry before
- 3ee00b139ef54c6597834b1ab6ebbcf2b9b687ca3c2f72bbb0d533acc8734bab
- this leaf
- a8aa7ea3cc94a4b9256e052af35474023b87323a2fe4af7e6fb9a8d4a6821234
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- phw5hxko2z4rDz3tJa0zUsUFsPUgkqH2qldGy7y3mzDuNkzOgQfZl8ZFn7V2b/OU1S5fuBFJK/aTVu760LZFBA==