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
- 7edfc6e9a9a10db58c4c00e640718191ebe971328d97e0ba436f0f8dee672474
- request
- 6cd326fa140caf0262751f4314c8571f6f4ec805b599c91901d0156922d7af8a
- transaction
- a17591e71945ddee9ccb98aca207f09bc9bb16a73dc7f81e3967c6f4ebe8a767computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 943
the chainentry 943
- sealed to the entry before
- a58fbddc4977102e0e177b2b34a4ccc2f2010a0325900d8264281ec2923f8929
- this leaf
- 122d76f63b440abd0131f4bc91b4ff3f28810c23f5db2442d175d7957b8308fa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hEhVVzr7h6oO3Bjn3NnN9O8ewE4rWF9v7Pfa0B5roDCs6DgYO6zLIU2MO/l1ySD5QZuOAm++J/J4yQGglRLRCg==