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
- f0647fa81972a5d9e3dc9bc0fb87b16708e77f76d780709c3fd2b847478367ed
- request
- 6b999be4997d3e3a0612924de0b56a371439e5f63d9ac66b19f229c912593d84
- transaction
- a3e26884de402502b43cc9d7bbb77fe5c36ae3e48df823c8d66a9fef94704475computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24352
the chainentry 24352
- sealed to the entry before
- 224dd12b173c132e84afdae462093030e182b353ca8e89dd9d74bc1e4d26bd7a
- this leaf
- 2f8faf500cfadf0262c00386916d26c8ac0a63c23e22d5661d3fe3a44729ae06
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c7ne3y87TmjudPNESbKhzHS1544QJbCiZiLjnMwBOt5UryJErUajbKxbHQ3PGLGVgYdQ2AKQv4Q0HnUIoL3eDg==