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
- ee6228d272c7a952964a36c6daa030c78f544190371be364a9286e2659150b4f
- request
- d9a8af2101c04d5465e3b95e3c154ea10b0da2324e658b4f409e93e22a18157a
- transaction
- 887666bd8366af49f1b3474a196050269cfe7e15392a666165111394409d9e0ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39730
the chainentry 39730
- sealed to the entry before
- e790320ce6fc934426b0a6ac9310f54a9685c48c326330f54db47f51f7e5894b
- this leaf
- 4c64f84f90ebbf92ea86b86ecb7a49153199295f8efe5764fb7f8efd9db0b569
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XHZx/DHADDuy1GxXHYsZSps9c0PX134qXT0cm7Er1RgipnGCAeVonemps2VPqZff9qDAKgwIPXYPOwjyy7kbCw==