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
- 6cdbb7de762e82d64242fb364c03c3b6996d768e59edf7de49b64b931a649247
- request
- 6cf131fa40163d2e8a6f7286bb15f37e354cbc73012e62e2e20004618d62cea9
- transaction
- 23105ae470aae1d70d9c3a6415efb18e2876179dbb6053272ebeb24346f69b4ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8864
the chainentry 8864
- sealed to the entry before
- f4b5d5f2717fa1eee96aeba524b142eae1e8c135bb7c60bab9447db97b690667
- this leaf
- b872b156b7782b2ffca77c9ad7a062a1ffd2a34232a8509b14d1b3fe48d934a9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +I6rgnHmb2otrA4f/0cmJUZMaxrv08hkL6KP76tnLXWJGzUD2lLArw6qziWApypHQrmLi6cg1G7X39EE8B/1CQ==