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
- eabd056971df795ee623b5c323151b491d0f92b6a1347ff2d7c87b7d97ee3442
- request
- 74643eb48ed7de333c2965e35764e30bd7ed8720915c555d35c8b293a3d84efe
- transaction
- 04c18dad4802c172ee2862f63ee3021e995184c080e4033ec1e6242205f92ba7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30453
the chainentry 30453
- sealed to the entry before
- 97cc9cfd725a82071051bbcd692382b54b6e6a6c3ab6bcfe4cd58b61529b2d15
- this leaf
- 5ba2609d182e0a01400494a7f88508ea01a688621269f678083da1db6dda4fc7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fONUh7Y794TpMrkIcUN+VQ8OoCWFrNWPjYIjwu7bDsWgt5B6Pm1MLhhy4/udhOZqfpzLdCH0i2oD0kXhFn2GBQ==