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
- 4d1a36d5a1cad5a8fb9161c231d5dd8643d33f996a73effac54b481310be7574
- request
- ec581bce80412183e37d61d077e8b0a207e6acabafde16a74e7ac50a32cbf6fc
- transaction
- 90a2318b8ac367962d906252eab3c4a7791b2c073dfe64b1a4147a7011f5a430computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65208
the chainentry 65208
- sealed to the entry before
- da26284d573e33e35c987201b0f944d4eba807d96dd2418da1127b36e0b6489f
- this leaf
- 6da4d9110b588281b129dc4fec1336477dfb07593732e7576dda7708d7b14454
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- i9BP/V3zNaTOHf18evB+/yL4taEbBj4jEaCLxIfKFp9hn3MZAhdwKFUXCXj7AWFxOnmKGoJpHjNgOSv6ak5+Ag==