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
- db5ed7681fbc22c5e2e1906ed0781e467011370edab324d3fc38730662d69cce
- request
- 55f9c0fc35965123bb6b3808544289c3fb31e21e4e17668a7163856eeee6212c
- transaction
- a7c8c9138d16d0c7ad54ebf68dcb66f512051317763081c882afc53bc7a76af6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41126
the chainentry 41126
- sealed to the entry before
- 01cab740fcd4565a8c86d5f671529fb588c6d1a3bb6c905690b9738d105232e5
- this leaf
- e95317197f0be7b261c01a753ef18097cc73c3a1755f876e18bb4648a611f7e5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HOOckfKJk2peGL6B1I39tfyYz59w7LqSdfYgLBK094Y8Tev81VpJuTRvbOypKjN+zy4Nkxz/4LkJwm1pYon3Bg==