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
- d316f20058e141cc2b15a590932b339d750814c01b6e935db6791f24831de7f0
- request
- 3bc172a16989db640b1379a3f46c9cdfb019d21eec4e4b94c2cc393987ad3497
- transaction
- 33bc9a5fdcadbec6b637235ee6d11c6548213bd344abfbb68cc2004dd61a0cb6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29735
the chainentry 29735
- sealed to the entry before
- 364155c7a166c591cf419f54f41b2eb2f91cfb89e66d5482a71195426722e38e
- this leaf
- b941dc2ce6be2315b55b028d63409806cff532ef8e2eebf523d32ea23098f8f9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oDCSenZSbPHxgv2sPdd68R0valtuXZEiUmUDeWPmhHNOnH7pb4T5Jj5f58qhmh4+l5A2GD0CTOjtPFZrLNxNBw==