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
- 4d0485ebef525cb3ec32a22800dd07ea4ea9c5dc61db3508bd05bfc742e20730
- request
- 4f15bc2e281b11b69b20aa2ed1b0f4576b0649926ae7671c4de6dd247c2b7b59
- transaction
- 70f5d021d92117a78a4e7df48db0c63b1ce5ced3bda260d8214d1716f272f10ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48948
the chainentry 48948
- sealed to the entry before
- 95f537a1e06a82ce87fef1a823bacdda8024b8f54c902a0460b833e0e88c3e5b
- this leaf
- ea5381bc37e877f11df0df7c4a3f84b5d062c2e010bfcbc94232c10ba6a01cc2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EIxNDUnSeK0ussT92arYM9pnvGFDj5Jd0e8Ki1dKbN8vTLlfeF1+P/BeYpiy/R4Eb9sbzzF/DrkwcGErO5fbCw==