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
- a3d2d3772263da978e36260c4442f843a09be5eaa26302ca6ebacd668c8d11eb
- request
- 44a01046fd2b58318db09dd7101cb2e8261efd1333870ea6c05f8ac7c67dac3e
- transaction
- be0fb6de824e45f7d10fdc5d4d7f0c5217099e06f0cac631f2a659b66ae8e84bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53200
the chainentry 53200
- sealed to the entry before
- 5f4381fa2f9bf7202e6374d449b069a4c59e6142e5e61ade2fa0351bf6b4ba6c
- this leaf
- aca401dfcad09b0ffb259a6c43dd8526ed479e58a367bed34e0a923b67e8a2ba
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xbeuuwoFDAmwcdM1aOLzOIX6s57f/NXYdg63Nx3tOhqOOee3o6jJGJ0KeY/TPhNnxOYazPkkaKETpIzGaJ4HDw==