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
- b5ef9dc999dfb03ab29d91bf4f89d6c571a0d0fce1dc28c3ee3b7ceddc131070
- request
- 66dc356eab134c4229b0d470357e28aac08b313b88821f2c0556ef976f5f38eb
- transaction
- d991f73ff90ace606a5e56f871938f583b0c354cc5cd7bd37e3ea86b8e98b917computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60542
the chainentry 60542
- sealed to the entry before
- aa6f9407ed80503b0b93b6df578ec230ed8dbb712088d02360277faf38ea9504
- this leaf
- 297d49468a7dc55a683fac26a94a504489b99b0bc2abedc9ee77a84082e80245
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZDX8fDsrzllncq9Oq/wa2XiPsPwTQ5MNCdT97U/Pcm7MZom8UQSBa+ifjqW4mBDSmklFFun8IXtGliqUncQSBg==