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
- 1a1ba445b7e434ead430f14a5fcbb59e1ba33ab965a08354e74b013518a41420
- request
- af2f2a180584f674f9596f9906798640baf8300e91dc077bac87e6860aaad8b6
- transaction
- 560e51ec58acbe29a32ad1a16d8929930dd9c1df11753b90335f827a0343b568computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49266
the chainentry 49266
- sealed to the entry before
- 4f6eb707cb11fddba706196ebee531d5d020002a44801bf09e6967c4bbbdea23
- this leaf
- d5a7ba0ab42bd6d07a1f226e17a8c1e56841bd284645289dca64393936352b12
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Lzz9TyOyVKSy3UQNqfbBaGtKm0E+SrL11TWYlRHJDIsL7Ih7KZIekExRBOAh8kVzKCBIZKM8QOC1iFJ3jlNWCQ==