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
- a76741e43c8aea8f148cbad201194cce9022db2c0475e509e023a1b3688dc354
- request
- f90252121b66f0cd9abc39b168edae0df54f0a0d707910c21334e4130382f482
- transaction
- df82164245f7e739f9b0a45489f2b7b8073a2fa665dd2cd3af0a2c4962e238c2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13322
the chainentry 13322
- sealed to the entry before
- 729ddbd2a796f95563a31b973f3ec1f149851b2e44bb8bb01e472621219bfb11
- this leaf
- ca8c1a16c13d39a9dce7dc181d7bfa13fd50ba4fe4bfa434c98117ea11b2a832
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sbLi7/94e+sswRq6pVPvyai8HJfCeh6sF8aNurSBbWbYH3F32lfKQyyI0ixRvs5Lc0CqEFtUeOIF6lo6e0zaCQ==