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
- b4dde4250aa5bec4d5f4b25d78c8d26ee83a93cb8ea266519db42a2f31ca40fc
- request
- 84740ea2ea9578ff83c5f0a6bf3f22b76e950a40026e65c5056ab1e03fdb6318
- transaction
- 78ae4247c139fa79c804a695c34ae13c8bcd31f983aa926a78d908176df1af47computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45831
the chainentry 45831
- sealed to the entry before
- f9c75c5e5e9a281a2208b65ba11ccb1f0d0ce56a3d5b52412dd33d71279325cd
- this leaf
- 729cea008f6075e8ebcda0267b4d4843ab96941c98d4fc70e5800cd635764c2e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Z/pbNJA9ra4i6vYZU69I8549/wm+hHunI0++AnW+wE419no9cJ5zRpFFSnl05lgYv0fxp7kCbKdN4+slUEhABw==