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
- c29f1b7047a52744689165976ae37aad8cc53a556cd91e5bdc2f053ea5470cdc
- request
- f46821259b87845e1c2cc25f122c07fb368d09b8baf68dc148dd7ed957d76f7c
- transaction
- 7e212d61778d4f0d920751ccc374c01972621330f715aab70d83322a9a057432computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41580
the chainentry 41580
- sealed to the entry before
- 5da0dfdea41036528418c887ec55d38e74ed4330767415a894725ad514c96278
- this leaf
- 00e4137cd7bc1ffa4f218e6ab4172adb9344c989ffbe22c5597ecf8b6fdf9709
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jz10yXtYm9zXCTQedEwnwe3ykra47y78qjhWtg/Cy3wyGoyvlxsGs5CNj0vNkuiQt/R5aqPNkoscIUSmPzMyCg==