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
- 78f0bc440beb5faa89799cdc5958ddbbad2da30eaaa33677a81ee7996ffc135e
- request
- 7901178de56e12288cd6cab99831541fed6296778634aad9c9a7f82ebf749880
- transaction
- bbc8ff32a9d14b7f0fb748e2130b228e8fd016a8d62e40b0bef93ff2c2935cc5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32911
the chainentry 32911
- sealed to the entry before
- 8ecd8e62045abb5de35cc6204acb3bc8a285309e2e475b463775f060c2742ce4
- this leaf
- b1b8f5aa8841f15a9fd31b39a2abdaaeef26197e9073d1ea4cfb8eb19ef0eedf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kql5FvIoXUbdUd0sIBjH1oL3VS3BnCMteeuilhpb+t2EecmX11uB2+02Vrh3NEWADu+1m5mpT59XEYTPQcwNBQ==