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
- e8a0355177cce2427c9c0a93a47a9fac6ecf4e4993782c6587623986c3e449a3
- request
- f7f987052fa282662a9364fae857e6210df4ac559c8d7efd4f10ff4b56a88c63
- transaction
- 7b3592a91cf454e88c0d8f51af4bf7f2f00b59e1f7fb80d4768ecc0eecbd04fdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27925
the chainentry 27925
- sealed to the entry before
- 4f60676fbd85457606db0d5f1804937d89b9d9f46091f12cf75ecba2ef759dad
- this leaf
- 7143ed69dac3f1e2c7dd1da7cbccd14e160b4013dfba550681531c3a36c51fc6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8PaigmkhLY0BI5pCBslH3ICFTAIz17sSod9Web9yYSDlSamePTCSjtaRZYtBWjtkA45wfNTNJoQ8XSQEfjhiAg==