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
- ed232ed25ed78938e1cecbbb0f0a3ab7ce3dfadbf01414704fb76ddfd07e274d
- request
- 9e82ddb605a0f32ad6b07c5022064fd61cb6dbb4559579908a3ade79c67273d7
- transaction
- f0e952617f99073980faf69ea1455d29f8372d816735e8a49930a187faf1ec1dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1152
the chainentry 1152
- sealed to the entry before
- 5c6acfb699f9e44dc59dc0824054478b25849ec73f8b1512bb28fb7e647d8a9d
- this leaf
- df1427353b8a5f23cafb815bcd7d0dd8955ffa2b5f1b71f29d697c12be13c710
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ucCVua//XHfKZXvTBfYus713v9lckQ11PzjKOmjgwnPP4y5PtFXkBuVQjPXirWjlld6JSa63b4hGeQ0RGr2fDA==