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
- 9c65415920eaa2fd3f8274b66faa76a09d6f1524a5f229af0f0fc1900880792c
- request
- b6aa245f189c94368846dcdaab2ce9a2c5ad77605edc3b103557767073d29256
- transaction
- 601dcd342f7cf0bab74c0e34fbbeb9c738d415c48c2a28012a998c93f670baaecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38614
the chainentry 38614
- sealed to the entry before
- 0b0660b800997165c27577fcd1fd5005161a2a120ae31c8b97e86e8f846b9f42
- this leaf
- ec3657d5c9475aa12772ee4bef2b5d67be6115ddc2e230f00de4e13124e9dcc0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RGHPxfTPjnYEGOS4PIh40h01mgmqF02HFy6gQWuMkEb8d+1a95cPhDs/EjOqbPfZhe6TcXjNzMOk4IWUrL2rAQ==