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
- ad05e37282256f514d074888a8d67fd8d7a09239a84ce07f9d765fbc591da43c
- request
- 019a0e1e64b8ae22cc0f524f0135e8d8853196c0f1516707f260a7c81a017cef
- transaction
- 060b30278e1b4dd624bc8c0b5baaf09918b98f93a1dd30c3996d9a6f648c07abcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65585
the chainentry 65585
- sealed to the entry before
- 6ca9bc0097bbef5f44879193b3e2f8b3061e5e398314f8e4b38d7719059119f5
- this leaf
- ba669ec84102da3cd68f1a1f3bf76b9005c0b6d92a2d32208acf1a9391ebe74b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- M8N+SBQXnwAxBhb22H3iruLucnr6Gklk0raB7Wj71l6zjOYeLmdVnMny7an2gMWnIZQCGV++5ZzvwvezsJYrDw==