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
- 5e826393ba9b2b8d281dc6809457ca9f09a9da54e9a69fc276708707d1a5a05d
- request
- b9c18cf8689061b58c4f4ab7e4b994457c6ce522bf5b0d81ae05ae173f54ef25
- transaction
- f0032c9725df8da8cda6fa4edd8f64d610bcaddcd37f168f6c6bd8308c93c1f5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17027
the chainentry 17027
- sealed to the entry before
- 682a1d7f0e0e74bb66ddd58e8f51959aa4cc825f6e8e30885c2b80ed96233014
- this leaf
- 9d907cea4d741c3621d48e73ea2d3e569a53f9695af3f4493c63fb634ec84959
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KwQCXKVWJAzCe3dRj93P3VyiAozCDD4+UJz1ujX4TeQd9bDDwDqMg/SzqqRaKY/xB7RFLdDRt4EbbLwZHJsyCw==