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
- e27ca5b950a3817e1d2462b35032a4d73e864d45778f3596c0ca5e2cacf07aa9
- request
- 67cb989a4654c718396adccdcd2395283e06316ac1a1d1260beb052630b05ad5
- transaction
- 3719247e68f3afb7061178a54878973cf5f9ff74acd028f450e39b97fac27cb6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47763
the chainentry 47763
- sealed to the entry before
- 2c84f57fe63d7a113e5f442765a10a32f03e17d603f372050857fdeb9c235aae
- this leaf
- 271ae3746a8ced8b66443ae29f1586f970687808cf7bdb08ab87a1c0ca58968d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- P0qAbSSIPBUyW8PwiKQP8c9R2pfspRVWzMJ/uQE1punxrmgKgj6I6VSZ6+ce29QED3uQolsu5E9MK50VuZWrCQ==