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
- 7088183f30ca6bb69d83e0b48c086d6f5c626c8fc94acadc8d31fc546eeff445
- request
- cff6bc8e79ef44050b1ac44d38ac20cab7ca7c1fe5bb0320462560c74ae2011f
- transaction
- 95dea59aa41932159a36178c2c9e3bc65ec079e71508110fc1b91cebca199d0ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59798
the chainentry 59798
- sealed to the entry before
- 2b30a5657bbcb0af2d076425f11bacfceb10617a2926e343947b410d0b1c4c40
- this leaf
- 86357ca3ca6ed7eab74253e281252a2f8322827e01741d03ab264f505a504eb3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fM0d7ThfXEfEpyBthHcWCnjcXiRxE/BVRBmKSSxG+quj06WpagaagZ5I5n0SDRS2kHP3crbhEEaPPdKYIShjAA==