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
- a28b836202b2cbc37f320f7d97c90d1560ace4e47896e736c74af90b8f9e0767
- request
- c8e5d9202f582a2f2471f566f2df2a610339297d46d5cca46a03e0bc535e5d71
- transaction
- 499ab3de3ac233acd6634d7e5cc920a0d5477f40ddc8aaabcf227bd687023b04computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29929
the chainentry 29929
- sealed to the entry before
- 7889e2d6f3c1d855ff2b2fc44d95e6f2842325ada2ab4a5b99613d8a7a1d7712
- this leaf
- 3f60734f52410d05a9765d622d8a6f77b2f0ff18808d5bbe877a3da6ab152c25
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mKY8BO7Ng6KGc43TzYlfgtqjZl8uB8Q8Q8oHq/s0z0o40+VuAaL/pmo3qp5rsDyG0PRm/O7OBtxBwCKIfGb2Bw==