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
- abc3dfe3d606146f934fc93f40caedb68ed4a9e28dba03129d1ecf30060b3fcf
- request
- d1286f69dcb01f8646bb21074d330b12d51e5de59b655e7fd04e80b722da140f
- transaction
- b983d83effaa802c62ebd29d34a619ff8d6ab95a6f39dfe839ce0c70f7ccd4b0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20545
the chainentry 20545
- sealed to the entry before
- a734b812a330da287a1aceece350db74b61bbd438755aef575b2d97207ac56ac
- this leaf
- 7d12681ae27c8e48ce2d862ad0101f8d4ea5a34494217ceb7637b5eff2c16868
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WT1IxH6J+O2QsEfqvhoXvA/KXpkAu33N6wLTCCejAEsZHfI8k2pgFFio3HSRhKDHrF86cKNrJgJqEC6SdIhODw==