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
- f43f7c6075cc0810fa0738c4cf04cfac4ec9d9a41014ed3406d8f4e57b0472be
- request
- dace42ece3e76bcf69972ea8a043ef4a019e7df86f5b179f35ec11a97fc591f1
- transaction
- c9c17889743a179a0dc0f5739903033a00a334ca8dd065401c0d48eb28b0722dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34178
the chainentry 34178
- sealed to the entry before
- 8823266e364009cbfeda2b16d3a53ca7516a2bc39b3c023b82969257d9791ce6
- this leaf
- c8a508e4e7260e808b29f564bcc1d127daa679610e7979935c2ae9ad5fe34c39
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7ELEmJ7VgjGwynPQNrVWpBo5qThiM85r7StcGhdW4+T826KU/C+zLovzkm9x5TTP9/3+FjvIEsKxCm5RT+LFBQ==