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
- 83ce4c1d70e72a8e5b701676c9389e8e70943cc508ee375d9b72cfbc397fcd3b
- request
- 3b8ef23a823bd1819b90928174cffa334519c95f5a716b6259e58c8be95c0e05
- transaction
- 7ea3939a651ff930c8fb17eaea0f7515004440a7b21fc9b248540fd38561d638computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36258
the chainentry 36258
- sealed to the entry before
- a3d0c6d1f1fb39c136a52c3524f243249f00cbcf3b7034baf1403ea39035368a
- this leaf
- 73d38961fe47e195e77985d21d83edde552b8c36365331da98c608d39afa6140
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NPMhn3fC32jiBGOOBFBljXoUdRM7RpAIHmvufxdrFg7NqXJp9WiQE1jZdwf/wRAZA2X5jHPMcBFiyYi3EbVJBw==