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
- aeea4bc1de6cc896c543121d4604eccf41b903180b16af3bc8ad7a5f2142d2de
- request
- 547b903d165fba9d0e58cb3284a969b31fa9824fad8a9680d658b2757a4859b5
- transaction
- a5bc5200ea223cd54deac64ee22e73fd13ac67f3224b8294275196970f17fa0ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67711
the chainentry 67711
- sealed to the entry before
- 220badf1eed3d39bc85afb16fb4ee9fadab7892dbc8aaf5d1359bb4e09e9fe41
- this leaf
- 7d2f3c4719aee445bfd84c40688284a8273976b8e3d2ebce1bfafd9cc648a0a3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qQrw9bD4CqpcqO8Z2C6gFu4cfWLvNlujCYiwyht5s6fuZ2c70KYpvVuuSPIbGN8Mxyoj/CB1pJeKhXQ2hgODCg==