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
- ab0041dd923012411e89a2bac26fd94396524b81b46d5c6a0701aab23af53544
- request
- 7a5ff8eeb128a0f6b6cda14648f5af817a50a8defe1f2e81ce9fb9ea338e0f2f
- transaction
- 59cc0742973066c27b44e951dc3ff167de97ab5677578eb9887d192727e0047acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17057
the chainentry 17057
- sealed to the entry before
- 6f0098764820bc931adf1ab8034f8ae07a877a8b50138e956f84cf8777efe4b0
- this leaf
- 8aef51a1a614827811487bd02a45724844452ccbc607e0dd3f256df5959b3245
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /nZUbRDAhIxPhaXCxOQ8RKSeUN2eZIEOgzIwzf7NzgYIb4geONv4odQFQR5HhxoBIXaprZhB+fuOzrOlj4E2CQ==