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
- bf164d1e1743fd2aea8b51318b7c882646632c53a7b71545f418f45a4505a690
- request
- c5509e254f61e82875c5951dd953b60c8007c030b784484c9ed235abed54b25c
- transaction
- 2e4df4d88256de1ad873261f8bec23a657da9e6e8944f5c7348817cac2649a48computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73320
the chainentry 73320
- sealed to the entry before
- 636a5c462912ae0a28d352949c1ca593870da521f44aaaf67e2d95f6c19fcbdb
- this leaf
- edd9ce6d30cf91e2aaa7e2a1b5232ebe8886544d21089e0b791085ca1caf86ca
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3X/UzbPII9Tz8Z0au/iT16iDB+njwC3OdLBTZb9NGviZbhmsWHWZZP2rLu0ZJkq9Zx2M9PfBhkD4p6YwX+ZwBg==