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
- 7eeba9c581e4ce85aafe7f723be4973dcf596969db8a2596029e0da69ffa119b
- request
- 4739496da032d35ffe607e22ada5d66683d69ac2e5fe1bfd21b5da982e661e8d
- transaction
- 667a951e39c0a5026c60e8aa6b0c1d2e466f9ccdc99a25c94371007549615529computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39744
the chainentry 39744
- sealed to the entry before
- 43c270779bef5a664f326e738482f084a37f0f15778cde5725ef4321bcaa6617
- this leaf
- 7d9198b7e2ad77b272517c433d46d650a2a586f5dd5e8e5b6a168eb733e0dc4b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PxCrG/fE79twWs/04PTVXBQBzNw65IIJdW/5G1BXuqiziH34UWG1X4JicM8UoHCGCm0V3LYInF/cAPPQaOn9Dw==