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
- 7a95436e0ba53f418fd6b590e3d2ae889d084172d555396e079309fc3762b9f0
- request
- 1815038675f2393e218ce1de18e0d10b092e066e8f17b0525ccd2be4dbf76f6a
- transaction
- 1a3061b0a72b90951adf43ab43e0d28451b8a023a07ed0fc279357429f3290e7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59028
the chainentry 59028
- sealed to the entry before
- 54b7a2c0b9ec99e247d46b19aca7ef1d7fffa0b02883fddf223e1fb296443b06
- this leaf
- 60b5149dba24b9022b7956096e730f072f29f7f14266e20d8c4e56494a69d9a4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aJQHnxuuMlTFu30zvRiimAp9l3glIC0tzx1T0Rf18/w6wbebeEz/1En/W5vhOG+dHdoZuEZNprn/WLUQsqLyAg==