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
- a1338db52d5e1e93a6cf22204ab48278bbfe533db8d9548cfdf22d980cbe5c49
- request
- cba9514598026768da4e593e424363c701338b223d51d80c75299f32dc42f26e
- transaction
- cfb7a1e8b37f70366118cc8ea2d2ce9aed531c3607df675b37f89f0354cbf70dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49903
the chainentry 49903
- sealed to the entry before
- 6d75e76fe5f966b0db09a2264eb15397702d2116e503f1e0db3838eb7fd48859
- this leaf
- bbb310e8c4610ca6da205c78c3927c3b8d4b18fbc1cb1df804b8926857b297f2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fdP0sEuj8nk96mPEKYIrDlz5MqA7nAHoEJ0uJL58NXKzVRyKMwY4yDAjt1yK9aRSenDy7o7ljrdeO+J/uVv+AA==