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
- 3bf94f901430856ef1c699709b1ddcf773b15bec0accb1cf8e892dc85b6a12dc
- request
- 8fb123d006d4b82ff13206529066aa082d5d6d7a3ba464e16ac0cd198553694a
- transaction
- 40dd407605530c076af87fe0eac9432020d0cdf4728d633520f03f16ff9ca7bfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43179
the chainentry 43179
- sealed to the entry before
- 58aa19da388a19a85ed7dcff62567e86db8e327db6e6d8af5dc1b7d502b84202
- this leaf
- 659ed4844c39975fa52f875326d6221ed7016407c663044b6222ff5da858ce13
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VZ6S2XrRoVrG1/9rimQ1nCxtVRWXg0snhOOmQ5iELiKzl8659DYX25tXIpWeYkdql/s/9m7h+tmY0dzHH/izBQ==