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
- 821e31aa8e615899b4fa02f2a03497ce3f7769d428ba8bd944935c7a6837cd3c
- request
- 0a943b20ec929531f4de888953aaf6cfcdff633f70a2ec83cbeabdd29e296860
- transaction
- 73348296978bb85a4a97ec87d91ced9237d852ec84d8f627c82ab19e8f1d8543computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42094
the chainentry 42094
- sealed to the entry before
- 81627def16af2d666dad31514e54a7eac7ea538e95a9b9932f60291161ecc18c
- this leaf
- b178ad3ad88e846dbef759f8d7c9daeaa1d4b9c34f6043bcfac9bff53a9ac755
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- doAdKEpRtyj1O+XV7CQt+uaUW+WqsnR+ah7yNpq3Sng6rg69uFRdF7opYB/jLTE9kGV8uTlvUAx5U10MiiFRBg==