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
- fb170d457f2cfa0e7f7577ef3c4ff8f204cdf8145ef80ec52e2f82692fc8cec8
- request
- 11a3ddcf18b8cec4c2e13ff8d77ea0f02a1522c8112262bab9fe8f897a8532c8
- transaction
- 2d4629f33f77c5ddce24b42d196a4373cda34688aca9fd3598400ddc0a658b26computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61234
the chainentry 61234
- sealed to the entry before
- 55d9b86d3d72b882c5a3f2f5bdac734304f90ecd625dd6043cb3305d3568d241
- this leaf
- 0d5b39aee4c7f3bcd777307fee835f55cdc24b2e43c2bfbd891d16f3901ca637
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UC+/5pk+TkyniJElhEZzfJjFwpdEzH1Pb/+tMnuTMGIZrcxlq0HURHD+ohU8Qu7kz+kInn3/4oY+yXmWJDhzDQ==