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
- 9699aa3f78a9ce4145f02196cebec10ba4327db979ed987370242698fd6bcad5
- request
- f79471b423152975d0c33fa08cea79309593ac2393c02e400d8cbf396f2bf601
- transaction
- e394e461bab6cd202a6de9c94f9b6082c604cc96aa6e615109753831024822cfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61596
the chainentry 61596
- sealed to the entry before
- 39978cc8aa0f76745bcd1a59df89b687058dbc379f0c37ae7fb6ad61cb6dea42
- this leaf
- 4ca6e6132ac1709154fec82ce5065d5386461dd35e2a1117f90c818ac6484d08
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5HYIUSQ42eNCVUwO3Iu33GO21Cmhv+iH7FwP81t01zRsLREEvMxaJYN+2da7AorwzYpXfWkWt3wtBICImH8HAQ==