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
- 954722bc31d997d7d69f87d980b1e6ee9eb3a9c76224b8662828c0965f5d9d2c
- request
- c651a24766e5b15d051912034e722b4c07fdbdd13598ffa57f3d9c02062eebaf
- transaction
- 84326cfab00e9ebec60db8e9864352bfbf00d7b2cb3d8983433ce91ad80a4b63computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39702
the chainentry 39702
- sealed to the entry before
- b2432faf155238a9f87d069d9075afcd9dc633f3a09fa37f488bd136c6429242
- this leaf
- 475d252b1e6046ae4cb9f5d53c8e76287f39f175fd8b8f748c8e6ac65a851d14
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hk1PHQd2r3aSyV8+LeraOIZznHiGdiczp8ZioIGP+G14NSlDeDW2ZuAU0gCABxlZaER30bNQXmHq22NUb6e1BQ==