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
- e9196f302159c42e0a7ed87659805f869209ec091b76ef5ed8705f3df0b3b705
- request
- a227e9c17650d104d23ae7be0e0d48c6af88ba9b7a6e67cd31cade6cf087e4c6
- transaction
- 85a06eef9f5a3c32ccf86ddb08c526d4912c8c51f188586408bf27fc9ffe7cf0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45049
the chainentry 45049
- sealed to the entry before
- 5896026a7253669119031f19d11ea85272f49fb69250a56a604c0b9f0591f32d
- this leaf
- 5acb8debf4c541aaaa47544974351766622dc8643f5d2b844acd152149743290
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TFZtjPy0tyQm1DOsNTkjzVkeAAYYEd7ssQDh/Y3F8gBW3RcrVbl717VAySAuvjkEBxFCJhemZVgX7u0EsYeTAQ==