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
- 2f8a39c996d5542c1361d2b10b922fdc70d867fb966481d2216d3cbe7fae156c
- request
- b736d2b911faf701b44116b97d51a5a424c08aea6a292432f297884e680248a0
- transaction
- 8a5ef0356e241ccaf644c8ad72521da571d900d02802c6c9f2792c914a41767dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65958
the chainentry 65958
- sealed to the entry before
- 812e574545ad1d87fb8ec55458bf2b9d66ad75438deb6f09f376d796dd1dfb5a
- this leaf
- 2504a35dd6d0775f13d3fb74c323707d5de078a595ddfcc6dbe133d048f42ecb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- T28TjrUX78PPdEO5t4g5FvlmvIJxq/GrohcB+wgVXiOuzUDNtDYyJZuCaUssitVEInlAR7vuOBmQ9CXES1j3Dw==