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
- 475f886e340d8a345cb03b76d232c1caa06682b3fdc81a3b916bd70415329173
- request
- 3b51fd59956672bed07444089c2f4798ddb7fe70efffa27d02b4fa4c7176e33a
- transaction
- 0178e6e643bdf5c48678af025d9d1e3d8db90d6fa8652e3aa215d6498fc25f88computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62849
the chainentry 62849
- sealed to the entry before
- 6508df07819e96dda30bbde474f4f40abd0e76dedf30c93ffdd529a3dda613c9
- this leaf
- 6b1bcc1a570d908f6b99806e08663c0350516f51143fb77ad24a5836eaf14f7e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +HLUOMoF62rMne13CR2TtOMK34jrFwg8AkxgVuWRMWszejiCAGucEZ8z8PyJ/aKifQDo0AMcKlDkCsAA1mY3DA==