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
- a61991453720f83175809eba8b69ec54a28cd3cfb03498ef088f79b72a6616d5
- request
- 6effcf6fd3556d26647bb3c038e144630199134e4c029463a85d5203a38600b4
- transaction
- 57323811427a11c4da7a08f29586ea5d2ce847639ea54605f79840b491ed6acecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74432
the chainentry 74432
- sealed to the entry before
- 1c8929b7c3587fb090d2e8c524196f57b10df837fd49a2c84f7f74aa7dcfcb82
- this leaf
- e37be4c3158138690e528e5b43ed2f70d911f475131fbb3a9d7cbcf57187c04d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lvZZ3hyrecprZTq0LLppQaga/TVXXZO2lqaqztcNxnJwz7/fnuoczZIynoMUhZqvW5flfhCi6o4+Wk8Z2uX+Bg==