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
- 8c1871f29cc20fe0f9cac820e687dfd408fb3de78c7546139cbeae0fdcb2140e
- request
- e55a5c5c30527f0f25c19edde21f61ec13792bc6bbd1281dfce5e6e3a54c99c0
- transaction
- edc00e00838f07689bbac4faa211c1eddcf8a2795d8278c56190c774745c9bf3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67300
the chainentry 67300
- sealed to the entry before
- f5d7e04fbe4e0552bd8f82979dbcc20e978c3e638bac690fb1956032d0ffa095
- this leaf
- 7396a8c4301a876383042648d07bb633414425d8444fa4df397ea935a7fd0360
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Z2OMnPJ+OFJJi1IsnCM5UsSUZ4R/PqNjRiMdSad4S6IX8TjLFy4V4dJKPzIXUWtKHdoZSqRgxYE3xMEQt8UnBw==