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
- 720e48ff8409a547edb57c7b31c7c04afec76dc5ee1c415fa4c0a34d1e74d9c8
- request
- e16413379f725f7c033f7e4c3db3545b9b48485d4191375922e14a815ed43acb
- transaction
- 320baec43b43319c739db34c62d5e682f419dbf6bd173bbf3184481dcf99d42fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21957
the chainentry 21957
- sealed to the entry before
- 95f48b3fa8725d8b3cd40af2a3d62d59053ddcf4f81b87519cb940d877b3f36c
- this leaf
- dc68b63be1ca972c186714d926534a058aca744ebe81c7c378759f291a46df35
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- d/904vhZwLEEoiI1rFbcJAs4vR48J/Z2ZgXZC3jJzt8zabOtIdfXJ8QBhooPiRtGwj/ZkUnAzMQZUGdk+tTxCA==