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
- 714274bfcb41745638df9b15f8d3828332314036307de411b75cf2b1198f7048
- request
- 8b212f554a952ef17db8d19b5f711129078ded61325155ece3386f94e14f9396
- transaction
- 4d8a5351a66d4ee89d0c775280d0e3a341b5fd7d4742147e7943d5ea18866f42computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23709
the chainentry 23709
- sealed to the entry before
- 6427d0f3a52de226cf9322d6d9753da5d417fda23045d0266a177244c84730d8
- this leaf
- d032402a98a241116f5bd5404cc19af3260cf3bb1613fe6f8fa050655ce6e950
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fFQdoXx8AiS4V+YxCwhFKF7QkTjun+aMrEAw+gN7Rbs3D2K7ERqefNobqC+9FQ7S6gvdAZ01/KLY2sisRc/WDA==