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
- 07338bf0c06f91ad579f8ac89af5b2c01e19c9d9744e1812f201c66ecedf0110
- request
- be4db91aa369d2da69573ab722df0b7f9c93dbb5e348a42a84240ed45dd91205
- transaction
- 6eb2db025ae2692a4c4937e19837ec04fc528f3276378991d7624078a6c534e8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61403
the chainentry 61403
- sealed to the entry before
- 536ffee88ad247088ff9b00414445eaa08d915acc7c00d1f0966b28a37c1f18f
- this leaf
- ba6f79857bc1e239796e3bc9dfbd66bf6fe9a756748a6894502b721f95b10841
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3CtIrLWEZFiKQsyLCqj9hfgOySQjvOFJrStF8defh7eppgev0W8/8yEx48LZoTNgH9B7UeuAYDtbkhLGvTiQCQ==