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
- d2f191cba9f780d08580e24933c84248fd774bf6d954c8a528fbe2844385c6a6
- request
- 9f8866651326c614d9d8de50e893d1bf2287f890c0871835d2edb5537525e8d2
- transaction
- 0c4d0d3b92ce9a6b93a2d950ef5cf5fd23e23d54e607ff70aa8902ac630d27f6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56094
the chainentry 56094
- sealed to the entry before
- 8709a0606499d92438ea4b96617a408427db2638766b4d28fd7b10d5bd175284
- this leaf
- abc920d22806fb2361811e7cf41ea4ded55aa2589b458410a9d24ce44d039772
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DZco15Jew7gzt0hi55BfnQOeI6oNf3ywxxI1gG7Io81yyT61bqbVi0qHz8L/sshMIfNjpAYyC8CO+YQQFFYKCQ==