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
- 5c99836c80354af163447e4f94db56c6ea19bbeaead80081ff3b3b227da8965d
- request
- 40fb1e691de6558c4146b484c7bddf7815114e975f9b105591f887440eedd6c3
- transaction
- 1389f5c2a54b908f7a0ad9098bc11e04cc83b2acbed2b58b4c485a0e392f123bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71067
the chainentry 71067
- sealed to the entry before
- 80e9610dc42e867af63bd1a05302c7d3780a0e654152afea68423d344dedad6f
- this leaf
- 0283e57c03cf1d597f230ee2bb05d6302470a3151ae3286990a074602b7db5aa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B8z9p9meawuHweEmS9hZcSekoHKTvSy7jFW8MFdPgZMMQKutFvSpK20pFZeOQF0ACh4t4i0QBjRY/DtyEl80DA==