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
- d90b6ff426982470ce91b8fac25d13ea04d88a64650c431c0de92d1988a6904f
- request
- 4b938bd654935daac64fedad4474ee6a2276e19d4c423cd40080bfde387e3709
- transaction
- 4221edf8540b440a1349e87a9e05209b2ebb0c40e09dfc9cf00137de8c2e438bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44444
the chainentry 44444
- sealed to the entry before
- a0fcb7964d6e39be271c9314c1984182fbb310438b78d6dbce0ed02c13c8bcc7
- this leaf
- 3393f4250d2ed19df8e1916f71800d9fb780d7af57f75909c3238f9465de8f6d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gdknc3Sdu5AkzQfdgFhp8Ja0pgATj2Oq20Lz4SyVI3zyUH/KDVNS1ggIIgEe/HJRQbJaaGI4KS2cKoumX1sqBQ==