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
- a7bdd8bad18e80d8de8c535b2c8e70e5371f89fe90dc6600c7417bfa26440323
- request
- 98fd5b1224b3ea8f2c28b33d8eb5f006ae4a0cfbd93c12dcdae50da72ab241d7
- transaction
- 89d495adff4e0dcfe2360bddb57df93c95c65cf682b460fb477306d488c08ca1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2660
the chainentry 2660
- sealed to the entry before
- 7c77d6bc8cc199227bdcaa05072f527b3a456ff5765bc72c9b966818bff83d0b
- this leaf
- c9f0a2a5a630bdf1a076c6649e6796c6c55f07fddd53376c7f7918b9b122c7d0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Vsoy9av3XmZjKMOa2LqlfzSzCvDgXMYIYwFnjEfX0IimSL8C9nFynnIez6w2XnJIh58s5wur7s6v1btmryquBA==