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
- 305f515b42e7b5652a4a6cb9d28e20d456b067bd0244822bf0cd0188428fec0c
- request
- f2723fe9d9bf430255665a51551c6e5089075cc2e57fb89558e2f4099c755fa3
- transaction
- 23128eaf278089114162494d1ae650fed0e3856934c23d94a4785c256a3501cecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22380
the chainentry 22380
- sealed to the entry before
- e054a41d427efcec368e3dbac897bd6f5f59b7745eaff670fa4d9748263b3a59
- this leaf
- 475f4ea76b3f29c910ff0f1e8b17be226769ecb6c590c3fd6db928fc1ff860c3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8TP3LbltGEIROft//saca5Qqs06vPmjw35jpmT4E6yibXrrtfIsOOBoQUd/eQPbVmA0pJElYOGGPJ1NwaXiGBA==