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
- 6a09860114aa03a6c67a37070ff81c4c06f802a087f64efef39fdbd696bb827e
- request
- 960ac206b9073b0ff5662d2a34f6f88e789a4d88b419f68daa4cde2405d59f7c
- transaction
- b632315ea06b190528fc9d28b769d08429ac71e7a31dec394d6997aac20bd27bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64275
the chainentry 64275
- sealed to the entry before
- c65792fda03733151c47f1f7ab966c2ab284433117f1d999f22554fefbef352f
- this leaf
- d93ed7ab077eb2e81100a8bc0bdadae4aeee16b8fb32d26dbd915cae5586d272
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lxbj4ai5LHAuk/pG8V7429UiUdVOdvWj3TO1VBDvcdcJHzPqS3KO+5DkVV2W3szOvCxT0yMThvEJ9i4yzNqlDQ==