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
- f992bb292f78f0ecd540caef892351f0c48603d6a61e5f279f166852f48f7ae5
- request
- 0a531466a94a4d98867019aae5834faeeb496faa67878de77c1de4469edd3ad4
- transaction
- 4092411957f6983ed95dff5744c9d438cd8a129b9f9331670a61aaf499115e80computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70340
the chainentry 70340
- sealed to the entry before
- 3ad5668e9452a9b1eedb5576b07b43722b492f11b010b99ff9833667c017bb8e
- this leaf
- 311de095d68e56b935a7b44cf0162cdf5413170656b5cb417a90cd83a2c5a927
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5aZwmGWp6Zfvk11fqkbP6pupGIE2P3HL5tIiosbtQKjxKGObv+SqF7tDftbx4O2OSlL3Mj3TVxefi/ZT3JkZBA==