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
- c4ea739439e05e6a85a458565a17b1df1d9ff3cc411b5c6d26bdd437133ed45e
- request
- 8c049838860729e306a35d3c0c50a41b9a3300cb5f9b4d914ca14a219fdff6f8
- transaction
- e6db4e27e81f99d44ef414a3d11969071e0bf11a804a1289d12a89f7e3a769c3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20231
the chainentry 20231
- sealed to the entry before
- 4572c408cda8b79f05d3f5a7f82c8e03ac1365f19645adc5cbd879f726cff555
- this leaf
- 6a62ce04bbde394af620f20010b9ea5c3f95a65c18fd172bc0a74526291dd88a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zt0a0TZbyHWfSz/DTBtGhPBhof6O3X1ibuhGasDE4g0A4QQceR8xNtHPR6ZTA1uG/f3KIbS4oK1RxdmIQhjWAQ==