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
- 6fa932c21758dabb62f16d2f34c43a9461a7f878a3e5dc497c15a78100e33f6c
- request
- 0d6a394daaa27b7ff90d8c1da717bb9239ef2935deb0ee91f0ef06803590f309
- transaction
- 2eef992104dcf22aad276d9f7baf553b3a51aeafa77a6f4637ea4bdad459c0f5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2600
the chainentry 2600
- sealed to the entry before
- 031193839fb5035e2fcf86b0e38c00ae0590c213c96498c62f85242ac0d95f35
- this leaf
- 068504726ecb5de0170ef612f77e5f8806ca694fe54c6923a2524b7542bdce74
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bVtW1kJssfiaIVY6rqkxuR9yGPf0xLMZGDnlASQnrNFUBS69zKANCug6fSIVKVaIIn16DbmUgV8uu4/n/mQuBQ==