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
- 65dee371e6fad4fd0afd05f50ef3f7b84e535f1744f31a54bb139a287f7e6d40
- request
- 8aa29b39a7514e36f8146c2d8de9a66194e59defb62f8460e2c54a2487b9eeca
- transaction
- 9366f45457a7dc7635b7b6e86fb84e68b9e7360a6384f21a7fe104e780d9145dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76334
the chainentry 76334
- sealed to the entry before
- 0f3c2b1beae95866226e48f79c1c3fd21fcc16fcbe8bb06822267fffff7785bf
- this leaf
- 7ce5b8f956e96e22778a8c8fd048fe5e8cd933dac5cdc6bd65d2e514af88ab9f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KKVle/138gniaVNPrau+eF4HP0uE1xI5WBLWYjjO4nYgGZrAMdqTF6MkVWCMvE7i90Yz25ToldNYoiqkLc06Dg==