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
- 1fa141178b295db59ced097078318d49169f722eb9226db94f094fade7f2d8a7
- request
- 11df396cb8263b52cbb0769eb43ab9989b296110f7214ffb09e0bae0c939411d
- transaction
- 30e0f95be1020550c660282463aa50eb174a76f5f1ff94f79e844e94612b58fecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69072
the chainentry 69072
- sealed to the entry before
- 4ef5cfde2dd104178f61144a0432d957a17648471d1f5e2ff0402e042b016512
- this leaf
- 12b5472c2ca962b1a04943e4962c67253819dbcce6d89bc0e6d2f99306fcf309
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AbspkXWw1cLXTjDijjQywit21nubpj+sW4txFgjBY+nzCGaGi8shOU81cK0oVeirG69jaaCg1k2U5i62H9raAw==