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
- 7e7459507de35253b2d37028d95ce9837172fb388340bd6bf7b8c18d6b3d75ec
- request
- 1bec4829dba280549a27f590fb9ef328c72e71a4b891660badd910107e15937a
- transaction
- f78fa2b7136200cb3b94da22d9a0dd50d3ebd07533a895f61f3ff78780bb48a5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 691
the chainentry 691
- sealed to the entry before
- c0cd143e147e5c969a8384730419ed9962bef02c93e850a5ba02b9e5df8df561
- this leaf
- 36995833d54e05c5fcba6c8318cb677936f95f7772a267bb25600b86f2b9a0d4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1wjgBiZjJBeKbF9kKVW5+7nBs1V+7X9lRoXpDOEjD3MQSKBhPWJFhHuJJ1lNcfg4kfr0tkbfZneCRyUNlPZMDg==