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
- 86944fa3c2961d360daa8156800bdbaf2ce54f2c1bed563fdfa98b557d66254d
- request
- f34ba36f7add9204e76d2d6fc60febb91a83ee69444785a9fb0317e9ff659672
- transaction
- 00dd7d7c77ee0c84e987fc187bd56e2c2ed06f622691b265c5f89cde65746e2dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38422
the chainentry 38422
- sealed to the entry before
- 5037e2a45d2f244b59dc39b32c41f9cb47022ef9604d4a3c10ed8e4050c60213
- this leaf
- 8d9f49b5e556c0f4c126b39b1e1037124779345484c3acd1db584c2a39c7394a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YXoB8NAnFk7VnbEnd+t2378wflwhXDLYcQWcaBxbGf2QwuNCzvrfreWrr7hmsDJ2JLnyUJ2sRH9Bk4TV0sZ4Ag==