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
- c242e864c0f54bd6f62d66add5260cbd37126d6c05b0b28be954b77aaa5c6e3c
- request
- c20e74636f6397c2c8bbffeb546d4ebb8747523e100fe2890a90e7d6f179317b
- transaction
- 4fdc56c7db45375bd7c0f69317d51691e7042eb169cbf90c9855872a5b2407ebcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35267
the chainentry 35267
- sealed to the entry before
- e46ecdda63a219463f68b7d0a8e12a8c71281f900fd1ef830660e1dbc95dcf09
- this leaf
- 55f513b5c78909525fd3e35b8d31be0c6eafb7777af7bb59ce71eb270b812af2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SoGMBfqAgZzvIw7B9Zn0YN+/K547fFw0HXyBPqDYAODehv2RhtV5WKFOLj9UXoXUfnAcZ9Njg72E/1YSHo4/Ag==