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
- 1277aa76503199555fbdc40deca51e54e2d6b64b6bd58b7eb41e2615c317271c
- request
- f0d65d611968b4baadecccdde90c8b89f6f91b9781a04fd87b6edb21138d16ed
- transaction
- 96140b326cdad00bd95104ec4d42c064730ffd7e340aa49258849f3f7fb106c3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68118
the chainentry 68118
- sealed to the entry before
- 83f1054dfb436cf0333bd621b5ec006779f808874ba87376e44bba82d9038948
- this leaf
- 602fcbf628ebdaabb168ecc643755f043c68f601a5cbaa4992d94c4bc999541b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IMBEobXsQ2tpxJucKq9MfY9vWLaXbxIX5+KAvNx7BqBd3rl6O4CUg0UU/gVYEJwy9ipF2ckH0q87j27Ja4fXDg==