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
- 1a399621acd97637fb087d50eeb2643ef0193ee2626c46832c11cd310038a7fb
- request
- 3f3fc3b8dc92a8db0ef2e42f74cdc19294eded391088570485034896737ec5ee
- transaction
- 0e77f09731d43c3d9eb265973d28e3c0a57118baf0601c7b182002954c1aa4d5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30628
the chainentry 30628
- sealed to the entry before
- 9450850b15ff484cad14d235f7c506644d2152b708a295e49d00259c2d2c7681
- this leaf
- c94a4ea4024c775dfc9ece86bf911aa9100021590936ec9bcf4d09da0c191a09
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6KpO7kWU41zsFehHLKQvlZwP0eEtKlN4st7Lvc6doCmvCvQ6UfXd3ldhilRXe8UK1iVO8UOB3gnlP50G0C+pCw==