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
- be5f3f29fd2dc32df4375f56c4795d0f9402888b2e49c7c8e59eb108ce637535
- request
- 82299cb3875daafeedda1fc434deca3f1b379c00fd0828cf3b34b9a3e4b704c4
- transaction
- fe114a35c4531ec0a077a613b2490fc2a468278b8a902876b60292b8801adf5ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74728
the chainentry 74728
- sealed to the entry before
- 21ea3a4554a5b3892f2401cf3538a80ac53cd0e05809d4031a249d888c608b5d
- this leaf
- 641fbc59003cb7f1884f6b3fee73680f2826a66e55244fd18b5ae11a3e510526
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UjEhZ7hJ4aV2/PdT9h2WQgCnMm2RgH1wws5vAo3O7nhKl9prX4ZvrzTNaGT1dGSymHv4dlL7j60PFt9fGCoOBQ==