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
- ffc9e7e5e6bf3765bba396dc9714b2caf88fecb7893f0095e889d9497c25f95b
- request
- b311b368c96418eae86b2ef2b470afd43028b8cdc21902baf51e640b8ab488ed
- transaction
- be0efad3986cb733be389399fefc71f6e1d3c859e26326d385df7de9ccaeb0c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7212
the chainentry 7212
- sealed to the entry before
- 2462984a333eec74f4a1c8c67da4d2dcd95ae215aac27457e9bc26055240da6d
- this leaf
- 00eeab547877e153d8ebc20251e1cfbd137f4e66a1bb221e2f5b6d078326d7c3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EPKeuEfqoJ7CP/MnxfEy1UWRWOgsEIAJHdL0IvWnGcW1nArYuwedrwAzALFtSbfTnpqM6MmUbTC5IFuhR/TvCw==