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
- 7ce97a222fef877917949fe93c973ed1558e39b9391f2e245cc615f06420eb8b
- request
- 87f25b49481ab4ccdd0b0396e53a10b221da5f0c3e5b3ab046944c6822b9f8a6
- transaction
- 3b357b5724e82c3cc201d4d55972171a7e89aa3557e75daafbb8a2a5ca58e147computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72229
the chainentry 72229
- sealed to the entry before
- b71dbf88fd5e95f081a077e0ff0c15f16416ad750f24dd312c832424a1358d64
- this leaf
- 5c00954aa154b2eebf2fa7d9c87250853b0917f30ac650790e6a0065c8a5e427
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZkTaLVkBls78Lu5mqQv7TDaJ+IZC/lUY7a6YOIT1VZMBRorS6kgy1Sqd7AokinJ3NR1JllQ+PN0RwurXYB9zCQ==