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
- d72a6431418cf7af06001ead291ca097cf549f7d6ce56b5fa15899675210027b
- request
- d3a67961dfd2af4eb239788fbe9302ac010a3dedc79cf9e6b78f741a75e9e501
- transaction
- 58c1d380d4b7b07c8234804995965b9ca7a4db27b4b2cc78f3dfc1a25c827f03computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68620
the chainentry 68620
- sealed to the entry before
- 24301dea8ad05285cb7144041ea6071552c4743ffe32c8bfd2326a2d6312619c
- this leaf
- 231a2681efa660267625d1770f677975c75763470d8bcccc293e4e65d0bd07d9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AC0xkcoX3VCW4ELTC35mMzvUTXdY3jpV0kxwjLEz4bAfzkHqgKnFCFAxUNy9U0ptRXQ2kKx2ESY5/lONxi02Aw==