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
- 66fd11eeb162273bc853409b26ec36824c22af4820567f0841b4fdd3eaebf64f
- request
- fc15b6be1bd0c798d55328d7e5d29ce1aa9b702981251b7d09e0879bc5e1dcb7
- transaction
- c0d7b8772254dc02d351593c48b464597017217acb8e00877b94147f91f6e4a3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70714
the chainentry 70714
- sealed to the entry before
- cb75d210af0dcf454bf462984efa68598b2e0edc31a14c167265d2359f8586dd
- this leaf
- 32e305610a7ad9b0888682f36ba2ea0db5f56d740042c6f998079dc77bdf1315
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- V9SXssWlgbUUntBj7J/9doMfXmV9fBvI+tgIXRI+cFABD9VH7BgRi4uBoHvm2C0OoUs81gYokfMtoMCR8ZBiCw==