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
- c8dd4e4d240c96d3fa3cbe02d6c01fc662cd058acb9cde397d679ddd90777ace
- request
- 48b5ffed264f96ffefb418ff89e839f4121148b46d92b2e09ce93b53c8162ee9
- transaction
- 2380977c173c4b0809eb8f2d4a734c0f67b20a3efe9629c54e9bd2c2e39f80efcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31758
the chainentry 31758
- sealed to the entry before
- 254966e4bdc6c6083b28e0d13dee3daca1385c3666797d6b6b929a6d934009b6
- this leaf
- 718cd71fbbd71a18affe69adf588e8fe3b61832d2204ccab530b65f4fca2eb48
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 20DOQYXD5TZvX3FIgLJ5/63EshtAOTt36LvTvv858jo2eJvyF7lOm6PChqC/WaUiiwbwo5ZMmr1jtHr29lTUAA==