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
- 0d5eed54e58e1f454e95e291d85d59e497ea9d9472ca52eded166c72f6246ef1
- request
- ee6bda2f8638dfa9d9f0e086b378090addf43b492b91b4fb19e8c0c814455c73
- transaction
- 0477f66cbc280094895624285ee07e3fc247218dc2827d903902435ab4064fc6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74916
the chainentry 74916
- sealed to the entry before
- 973a908c014fc739009ccddcd59a2de0b0660d0932ac0834ef4a21efab8a34a8
- this leaf
- abe57d9032fa9864a67e09cd9976726151c9c7db9c89c9f6261047b42409cde2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fzfr7WFjyB9rt1Br3N6AhDeyrP2xYFoum853uagm+oh35XO3YlgSF2LU/UkvbA8Edi9eHAiUaS/YD3WkEbMEBA==