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
- dbd6b4067ceca00d673935460526abf98aca5b95600c9dd918c7633e67e79d18
- request
- 78d74daf4b22a99e006699587b3ff7a6ed6939266e50ca38aafcdb70b51d1bc0
- transaction
- a0bf43600328bf6f84003e9f9a0bbea3f7e73a4b3357182140e2d00b2a273c94computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17444
the chainentry 17444
- sealed to the entry before
- 0769da0b14838ff2a29aaf7c5744c47d174d9cf7540e17e20a9a26e69e03bf5d
- this leaf
- 35faab685f6f0a40ad31a751a7f4e8b9697b0c46ff59e1646b884ed58d0ea678
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9wxlVOyQ02P05dCi33nGHkVy+1Yq1cUgOmHYE2psW2Y9U8c1qFSkFh+P7jPGaNNzdk/7S60kJ5ejjqYlJeEaDA==