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
- 89aac0b57c36272e4179f64b12739d8ca1ac0a1c79fa5976a812497759c1f086
- request
- dfa0f35ed6ba2d8e16a5fde60b848888d44cabe569cf33cdf19d25852b6e0afb
- transaction
- 887347921eced849077210312dc967c81daad0dc9e6375b8ef01113eb4fe3106computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71495
the chainentry 71495
- sealed to the entry before
- e51bb8f39b13f5248621f1499680b01e299650efd8ade07e418d4379bca95584
- this leaf
- 8044c1f95606b7794efc5311213d7cc1595b897cbe118952a8010ae17824f900
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lsLJse72586C9b9ux+JUvgD7F/WSGYOhdvWUzGuOHzWxrbimTpDhAyw/s4vtvbfwvlvFqePc2IsrGm/F9/HqBw==