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
- a458799e854a6e72c2ba340b8939eb210b4882776f10e26044bd0068204a4fc0
- request
- dc2cb275e47bfe58e88f9ef5a2a20cb438424296c9d34b7995ffa2c9b19a1da1
- transaction
- 0cc0fe48903fff2ef4ec9ea90605ec719943164b3d84915a50a10e3debcda958computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70923
the chainentry 70923
- sealed to the entry before
- 1c833b60df34e74166d95de1f9af50834da7b6318f49c7f2517114d0a11806df
- this leaf
- 636fa291ae3e9a3401317bac8663f62e5aacd90bb5fca4de391178a1d5d8cfd8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fVvFi8sgLndWiv61fVZsUlKwPJtuWMVoEvI18lnHtO5P+ZybvA/a3qDiBCA1nK9YGuKDyuf14o6+B0VESOQ8Dw==