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
- cc94a7a9ce0b3a48d355c2dc35c867fa5a4506cc014247d139fcc383883503b4
- request
- ff615a1b72c006985cee18a7676af086be28f94cf8966095cf0e44d092878d53
- transaction
- 084442cb520fd86520aecf6f2596eec807c003285ee4749fd45d05c45cb7c591computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66725
the chainentry 66725
- sealed to the entry before
- dd4e84ad647f9a3e35a32b9e0f3c13c3047a5018f29a00d919a4d972c07e8cd9
- this leaf
- a2034922bc0457247d76f8ad9baed57b850810f614d419d0a21cf8a2499e6dbf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pRMnARyEKicEho9LMAjdLYACvPnJc9YOuHvHObQdCEWcZMVzI3t2X3LotTGYqe5/As+EkZRYb55TmEDIr5w/DA==