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
- 8e3f96f98d3c2527210b8d048ebc381190ef1a538b5edf2253d798336e7fe7fc
- request
- 85de5a70102b356d8f518a43849040853b02824d6c23aee2bb58d28c5d4f9e56
- transaction
- 1a57019711d3d1f417cbfcfe107d88b7f1e134d101d099f6a06915e22cf65829computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64815
the chainentry 64815
- sealed to the entry before
- e8fcc024dc8b25eee2f70268b0d4ee01ff55f22ead1525287373621e404d12c5
- this leaf
- 6496755ab5126966eda05fc94dc54946a54d296565912c1b13a00857ebede4cd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xglTd1XfCW1Viopb0SF79DMOfHM60dZJaO1WEv+KYY0YZiPjUmr74AMtaCLjW7Lzb9i9Pnj4gpbRDjJi0m/IDg==