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
- 3c04196c8e9fc0ddb4e2a49df4d995df1fa01dafc09835cb11133dd1503c1893
- request
- b682a2624735eddf5c7c391616021901c19313fc80460764fe66ca9545b3745e
- transaction
- 290e9dda8a13c112ca5fdcb935b21f3ec4e5cf832bcb973ed1a7454ac254dd59computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7297
the chainentry 7297
- sealed to the entry before
- 2c2e65caae4748b2ef0d6b6940a88e1a2a92539d4300888eb80a35c4ef2b49ad
- this leaf
- 960df91c903582e03cd633ed90936ab34ed2b531385fcc5748982e047f82005a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9tP9NuMgyOyFDOxykDL/7rWiSPCIcdwSCndEFXy9QwEXgCxggAR4IVLzqN8GEPLCEXaHhNdUqCCcOsmjyuhABA==