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
- b19d1792338dd9c0e6bc61b210e454ccc98bcb7d492edadefb2c456ec2f3e8ab
- request
- bf431d9fa86ed3fa8d7ab3cac328809fb926a2e109e452bd4426feb32688e828
- transaction
- bf845e7c83d01fe04ea581cbe8c1e70475d5682ce04725c855699b6083dcd23ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42312
the chainentry 42312
- sealed to the entry before
- 95cf77c4c46506dfb402266d67cf4ae751c3ec5b887e4fb6f010da6af51b0865
- this leaf
- ad0920d1ecd3507fc7a4f61e76f6af8b6a3cf9e4e1c70d52ed0ddcb9ab6e498e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fM7MMmAFqQKM55Ej/Tmibi9LD6bGmaQmpV+b86zKlOzqWuxWfHYnFZoz/IB3zDlMh7Sh4tNcVP5OmLlNAPYlCg==