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
- 3f90937593ac9f6d329baaf0596fe0826cec5a814c2151aaf869328f1a951213
- request
- fad269a0d59ccea60e5813d02185a320162b20f9a3994464ffb32bf0e2714c82
- transaction
- 2758711b7a201c55523ed632046fc58d03a0bd13fe1b9f4d0c439b0fcbbaba9acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50165
the chainentry 50165
- sealed to the entry before
- 4925d2ceb260c006891907206897a5ce77843d4abb75754fd42e79709b802e9a
- this leaf
- fe39901b85effd30b0ca66be17472989dea013fc6d95fdedac02c56eb6e5e81a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oDmV9S4Gk2PgMjNy1httVj03NrpSF3yaTKQdV+7JplxGu/v5guopk07sGv6jigRJg2djHlYmY1wYwZwwNvhqCQ==