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
- d216273d04d00a589dd3340a1124e320e4e5fccea3f18b00ede9135ac94b4558
- request
- d57daa9a87681ee130123c529756dfa24238a30d64df1c9cbc1945d3481a623d
- transaction
- f5810ee140895f1029996191f85d9d0c392ef853171a2223e57553cf981f68f9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70011
the chainentry 70011
- sealed to the entry before
- 26f6812775ca054d05c8c66e24e0ddf6b1e048ab42e144bce9d091e56381aa73
- this leaf
- 0ab3d9886b008aa09e94d40419b92d00fa0d5d322e5c9d0efc2ecfbeb6d60f9f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3EqnlObBZqLTAFLvQzW2kNUyekQZRE4c1/PAVW8caFLlkDJnDbSHqU1pn4yZPGzpVYhz+5j16Bgl+9mDUU3KAQ==