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
- ff5310f4196e17e909f610c60cf40f25d960b959bc3c4270635b07e584ffd39b
- request
- 442b46f85379110d4dae0729300b6747e082e7c18b06204ad76e2993a1c8a018
- transaction
- 057a82a260da3f2810ddd92600c9626d611ca59c9dd519e76aa411dbd9af7bcacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32022
the chainentry 32022
- sealed to the entry before
- d8a84cc15ae9630c36eea1ca7373c7dbb050ec1b110f03074c054abc40d7a24d
- this leaf
- 6cb20c233858f1039ebd4997790d532030a4f8681e8206fa86392bd523f209e1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HJ1ZjDNZjw0RlYb5W2t+wIIEybR/z1M1ZOVAV8ZB54ugrwQ0pvwKgG6CT0IJFj08rnX6Q2flBnmjbxE/My5XCA==