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
- 25f35a48c315390ba6694f1e900be006208d5b28383e3513c5203d7bdeb8a09b
- request
- 2c3d404361a0ef06b9b6232759417e8654af6e9259f3fabcbb0cbf64a64366f0
- transaction
- f9cda8217080ef2e9513415acf2aa3ffc9d27cce066df74096ba2f0016a46bd7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13141
the chainentry 13141
- sealed to the entry before
- 311b21c6cdd3f3d1ce9e7e544f6b861397cebf9ac0651dd6b9a4b8703e021097
- this leaf
- 0e44f6463cc736bc161eed5849b39e00cf050e03491de650082688a6274861ef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fa8J5QfwwUWbxxBZJYIP8BV2uP0xZl0OE5Z+uARwmW3yakDpOpEplYL4hK0aTLAYTz22yroVT2oK4wl2WhzoAA==