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
- 66a3ee3f8f2d487bdc176c14e75238328be9bcca33ebbee668237c2c4014dc58
- request
- de4477768e38cbed12ee6387b5fb7b227e43637b3262441be16e0933c6f600c1
- transaction
- 1f8c315f9e037e990f647d20e1219937a741587ac8b8ca8851177512ee457e56computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41500
the chainentry 41500
- sealed to the entry before
- 6ca4159709dbda73d4ec8e1975c0466131c08201c3441876104ce44a90a6caa2
- this leaf
- e0428a49f4f38e2fe809c548b8146c1588745bb12df629b4c9ae70c3848def56
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- axnUUKkQmi0Zr2Tdbrr2c+k9kENaMTQ+KH+CYVwVB8CteQk9Mb71iSLe1uS3Xv1YiIBQBQ3rPqy/U0Ba5gqcCA==