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
- ac0e240088e20c79c36f6f0972c1db8da1ec443c7e8626e56ee853a3a2599b2d
- request
- 2a5bd6cdeba133b7ef9947142488888b40b59b91da13d20dccd4af0489650187
- transaction
- e25fa2840f2b43b84f7844eae081798871d5f96369e7740a3825b0289cc735d2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69353
the chainentry 69353
- sealed to the entry before
- 8bee3538ac8fc1a919c529701765b898322855e089ec66f2c349fb07d6aeed6d
- this leaf
- 19cfe82711581c805d4c29431d4a57eae2183c4683e4bed7741148626d8925c9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Zj3d+uDtSLYzKoHAtuxDnjvWDEDB3KqJETZeP4hRg3lnLmzMrr8OjWl5BdnA+QQ3e6SPk859lumpuFjKCFYvBw==