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
- 95f5f780ab3b064bfe882407758fa188bbbdb2b6735f195dd3efde53ca32fe00
- request
- 45256750c50c86ba74fbd1e0e72ec7c3e94a8ef81e2dd7f440db0433290c412e
- transaction
- ea000057199f2cfb9493dee78297c99286792fcd0bdcbdb734f51992b2dcccabcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72210
the chainentry 72210
- sealed to the entry before
- a3ed80bf00c8855fbfc7cd404886a0b96e3e18995ce45ba876928023b97ed776
- this leaf
- 5a2c6283be318ad46f71d6e53ece25005ada32c337c7d9cd57ac75058d7f4f6a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2pJWYYgJTkQ97p14CJAybGal3PlsIETU64m0SOlaxPPKY4F1C8EfCbKISjiX1gTMylC/8ejYgHCzt4RUrIroBg==