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
- a20d79fd0d2392ff2b34d0443e7ee80f01f6d3583438e4af6516d5447e62404c
- request
- b382921e0843c0044b13250ed6cda97620ea725e0d03810ea1ff7953fe004d3d
- transaction
- 0f25496e52a28c0d172e6f5f7d2469afa64b650c159ada279f8efbf147661e49computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64641
the chainentry 64641
- sealed to the entry before
- 10dd5e7ce968e57f2d8eae0105450b4126c503c1f0305024dc53438a2a59e0c8
- this leaf
- d58058b45a675fd690d6e75b02b8c352976a6995b02d09844133a61de7b218d7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oUELqZUMLFyx7ytOsXyNIkE2ODtQSW5muqIMNmCFujqyLsVxmAsiefEDXBExMwC2kHslEHkmtE0Poc6V5VmBAA==