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
- 973758ed03d12c9cb3f21cf1af00d8d5ee5af75a8ee28b2d16de3a60a9717de3
- request
- e3191bb075634434055cd19502d0cb51bb60fcccd901658cbf4dcea131d81d38
- transaction
- a13f5e2049f218218c2f6e7f55e63a5b1959b6c3bd479e3fff36996b4e2818aecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64653
the chainentry 64653
- sealed to the entry before
- 7d3226a2cdb6d8b75b40f02c3db2809d0335c0c297adf810304206258624f6df
- this leaf
- 7f7d17673875365ab952a7b05a978dd01537392042f2b3c64020bb2ff713b7e2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WYUkuBedeJZsWd7ayjnsPXNipb0XKzck/zfzHMpUKrHH8ees8Tvv8qRu+lsOM1kmKDC1jDXLwjfYQxwUA0PnAw==