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
- dc6eb72ae65ed9dc12151bbb39db91452cb41c2aa3a0ba588d4e181b22bef09a
- request
- 3aa014831232fffe4763e28f415aa03dc062c5e1104a3fa52c8c4fa76545a669
- transaction
- d1bbc0210869b0228422a830cb2007a820a6ef34bc93444d64d0ae6ee0cb2595computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3220
the chainentry 3220
- sealed to the entry before
- 5a4d96c1943ebc802600c36e061ff9c3983abfe2641539cd0dbb4ded86e92b22
- this leaf
- fcf2b5b860f91a9aebc48f99eeef0f518a6170ab2c3aff740f90f6a955be8cb7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BJXCaeho4z1r/b6b/gjHHQmpU8ZoD6AAHATPHaDlH/bvdIO68emrdFwMh0u8aeTBBZGsk7e+UIB17ONrwbc0Ag==