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
- fda0daed9455eb567965b2d0393cb99cb39eaa0f9fbc1ffd36504bfe4bca2780
- request
- d2fc35f08162cc759585f61a1ee008a208bb464a58693c4e78cf4ad8ee1a4fe5
- transaction
- 8f61b3e92d661e499d905c55293599730173b57e5b1307ef6376b6631672e5dacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51315
the chainentry 51315
- sealed to the entry before
- 601159447df0a04c569d09ffa075fde38edbb4b8896ffec38da933932c1a7860
- this leaf
- 2e90dda72beebb70bef6061063ec2dc004fa8d4f584f95a475ee4fdffa967367
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dINOF9NpDfkfF3fnHdx0KzIsYbYjw8cbyxGIHnZcXyDCr/AqMM87o2rLM/gONlObp7LtzUTFW7JSnQObqLPQCQ==