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
- 67b758a815c8042b981de836716cc81f1c376e8755856018eaf921ff81435b3b
- request
- ee44666558ecd4f08aee74e29baf0864315ef147c4d59a0968a58c14be019726
- transaction
- 5b3e2c2397318d9693ad0d66a92499ce241162de623eba490f4a208b2e4a9f6ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24799
the chainentry 24799
- sealed to the entry before
- 71df4a401a2870171462cac049c1f980df1d91de72dd4fad89d7ce12ad82e086
- this leaf
- 9af4d26e1cfba386d16cc65a1bd8ea629b97f1751f1f8bf1f6fe0e7b7c7b4dc0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fVNvb4zs+tnFBPh+9veX9gjXiM9SM6fYJAPpWx3gczMwpjHlXBfAEQbnsWIVVYJqdK+vaAbknQpLEpn7jFKiDg==