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
- 955b8efc206629734c44471baa71dc0aaf6030655df1d1d218f139e3a3c93ef4
- request
- dc49847482b657ad2085aba0a764e064c3ccc85ffb0fcb4c2ff7304337cdafa9
- transaction
- fdbbdc277e4bf97cb7410a8d1929f271177a97c5ce1e233e1f57fd1f5c438986computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68900
the chainentry 68900
- sealed to the entry before
- f084111c22e618d44cbe5f1bbd27216ac775168fd5456de69c3678f56418acc1
- this leaf
- 014fd9559cbae9019d5f5d94f8523cc5bfc424524b120b755d25879642cf4c21
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UYEKobFJheNCkY4ee5dpxEbTlDnoIdrLCBXcWT/PddxLesd7m5F15FaDfDPAHbXtzGGnwXUSaOI3737K7S4/CQ==