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
- a31326b648c2ab7554c239cd38e4a16515c096739289dc93bff8c77bd634572a
- request
- 36e20b89adede23b019ec234e17a7ee672c0debf447b29fc34c6ed080d1f8c11
- transaction
- 2b12b6b7265324d69520cb646d04c85b1f4bb6171fce69bd95b774f90e8bcc25computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20088
the chainentry 20088
- sealed to the entry before
- b09d8ebc23fc45744e86db9da65a422c6248f71c2302c59fa1819e8ec96284cd
- this leaf
- 150e556173817f4bc7132016d5f6d21b7760838689a7636c72084a34d7df512d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TV2cbHF6XSbBi6ocC/YQ3gktbX7mV6Pm8NyRVeZR4YDyhjj7IRIPRutn1SxqC+of3eTa8bGJeSjGoi4ZXelgAA==