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
- 6202b6aaa519c355b1013d1e8450c2edc8de1abfebdf2f0bf0cd03d7cbc766a3
- request
- a4ad937ef12bfe3f8848659a17a6f34714b760c380bf78e53ab9a3f4a3232d00
- transaction
- ec4e7ceb2f0a27e9b9a61870e6f6301a26a1ce08f41694fe3ce7ed4d50fde30ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77796
the chainentry 77796
- sealed to the entry before
- 1b919a67e8681dd4684bfa98900ca3d0e7bdc370245a899030053ad14aaa32f0
- this leaf
- a45f7effe00c8735cb53527ac9b17b8a62db062220fba725c3777c1a21325ccc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dwaK5F2a6E9slsc0BU8XDTBOzCJDwrlZ4bSwS46/b/N+fV3x9mKleqHIU6siyU3qcEv+ugyCTNhtL1wcrlDHDQ==