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
- f1b3e86a6def83112dd5a0aa459d6cbbb55e0810eed95bd22ed381680e2bed23
- request
- 3d6f3032413bc4cb8be7cf6059194cad861c6402710cf4e16453ebdd144c1352
- transaction
- d879f5ee3a5a3573f17c9470c1a23fb74c53092845b3d7c94a91c7136bd58b22computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 366
the chainentry 366
- sealed to the entry before
- df31e0a414f63dc25f2a235d958698110135c0e854103e9ca127ad9c6339fca8
- this leaf
- 6143109e8c8a1e1b7783b57b30023c532d99e806dd420f3488d9907bd8905a8a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WvUk9xw3354jGihTJgmlSJQOBCBRqtyiQyH698dXCqx969tiuz/6KwqtDrTTFEx0A5DcMeHdqa4W9HGrek1IBw==