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
- d69a6fc45741ab0cb8d0706ff2bdea2c5a09261f5d903ac7b16618bb1e6cda2e
- request
- 805b2eb2f8317ec83674e7301472203ba5a8e76f3b1829dccac8ab5342383978
- transaction
- c6f11c73ef2fdd8658ad3e680629bcdb37dfaf8b7c1a29192bc71920adf75272computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55502
the chainentry 55502
- sealed to the entry before
- 7ba3d648139a4224665875e3a159459fc98d8b440e0465c880f3331330fa270d
- this leaf
- acb45ee0d5fc60995594ee511c843320bb3b5a2cbe6a9c17a94c0da3145f8e9f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lLZjDZwBvIYKckZH4fRE109S90f8kmuggUD0XUZoqCisCh6c+i9CU1kanw4ZsNNi+ffGUGsM8lYFgQNRU6V3Dg==