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
- c9375462f2df7ce6d0950b77b8a80d85c53603c3aa964feb056f731b8a5aaf8e
- request
- fbdece63b2403bd3dd892901f246613567804541573dc528c38672e0f7c64b62
- transaction
- 5401fa70c6130c838047330e18ab7057e4fe2a8faa2e13654d24438e829602a0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10957
the chainentry 10957
- sealed to the entry before
- a4c5818016a4e355a41ab2d862af4702bd215139c91a37114b26863195435675
- this leaf
- 81a382f5a8fb2a7b88db522ac45aad91772e85275141779f7fb7c3e5d45162e3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- v1B2DwkKusHhgsEry9jaCZ9M0VagIUomupkQVhDIbtZCzOuf9C+/YJpqZY9+egd7Ip+fKjem4FSls2OcyGsxAQ==