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
- 3f736d0064c409cafac40e88698f2d7f0ef8de085c5fbeb67be3d00826428bff
- request
- 47cbf05dee7e90a4b1930ba8c919360c6759c0d107c2b700e42ff7e26ec06085
- transaction
- 13c372cab13b87a838477573b68feff50452f35e51a5e7a27240288f6850c9a2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63597
the chainentry 63597
- sealed to the entry before
- c3f7021a3ebc5e89657087ac638025ef3d06507be623c5c8f080b795bfa4c4f7
- this leaf
- b1fdd71b62b08f63d9b75ceabe16da2fd1ec42b782854911c0781cb9dd1cd718
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Fl4LHd7rkhR56WiiNHvNLkhhqsCeSMDTaApo1Wbc4InZUIN7/pnlGjK6+lznjmGl/aHhkABMYYHmalAHUrqcBw==