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
- 734ac62ddb48de3f553af6ffe01f7b97ec7dad501955ba838e5ac4af48a921b3
- request
- 1d5f8f28a319ad8926958f47695a1f5279385ec126cc619755a9370a87b92447
- transaction
- 12a4dc322b31937f23f48470b75bdd36200273860a06d058fb62f197e967c7becomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36662
the chainentry 36662
- sealed to the entry before
- 09f5ee2df55e1567ee0a3b59864e4a63de1299175fd66f7b0476d95ed6538766
- this leaf
- 9963333a81fbac041895c97beeed415af00d1ffc5fafa087494f3df87630a036
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UEquL/Y056DvKPJ+rWqqzGHLPECbwzRsQOlMfDEajL/Ltr1hcZm0IPoqP6K6Vm+m9Oa21YaEkKSLyYgAF7BxCg==