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
- 20a6e62bad513a5e3f320f6c0c9a8199cb426bb8482691b1e9f50358e8b3c879
- request
- 99df6651809c666849eb546b9c207879e8904efced2bb9ac1d82719f62b69437
- transaction
- f46e613d2e2211855c563a3a7637679397e42ae5de8078a1ca6e2de81b25ff93computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77548
the chainentry 77548
- sealed to the entry before
- 888f3128b911311ae9a50c3c97e3a1298a71208dcd4cfc046d20eb50d52c2614
- this leaf
- 324ba3259cb1b7d8aac6c2b5aefc7b97d77ac2a5b0a619fb48926e48a312d128
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bt1N70/HhORTzEtVeItvCy5niVp3bF8wYqmHaBIA+mS5/XU6tmSnNeoCuIjP4+b81gbXLdGKQybmbxsnvlMVDA==