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
- 6dce462805bceabcb01755695d14c1939a7d7612cd3b2deecd0914c6abc4eb56
- request
- 3dbc797fd3f99b035373fd36b33cfbd7ff72d1786a0c63b57f0ac53359d15d49
- transaction
- 7e063a41e87660be6cd81cd873c8982510a827e13f2fe7a0a3af6bbcd1bcb610computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65025
the chainentry 65025
- sealed to the entry before
- 8d7f8ecacf0e141cd0023624c7fc3133384a7231ceb878d16cb8ea8ba78ce93b
- this leaf
- adf3ba366aefa1c9aa0afb30ae6b896e0fcd6ae1137240fff943982d5fb7e89d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gkt4DzllA9LFvKkZJPhYB3t6OHn9WDkKeWGMRSMst5ONumkRfRyoKmEcJ5HH8Cj5/tXeVOc/kwhh0QBkQbq7Aw==