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
- f8707af533b6954e22c4c999b868bd8e259f4a193e3cb5222da025aa6453e58f
- request
- 0265a90ada07990db107cb82afcda1e53ad1c3ec428f3a97b79b0ccc94341d2d
- transaction
- f43fc9ae556d9ecdda91d47b5d20bec46078df4ac41f2f4c42568b92de1dce6ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14172
the chainentry 14172
- sealed to the entry before
- 3f70ab4d1b18f5e64a9eab230903fb2863c9deb5aeee288f69ccee37750e5d91
- this leaf
- a43f28ad4ac88d8d4fabb3d0ff71adb45127afd9d43db8e2447c70f7b4f427d6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SBdtcK/alVGACgB09nY0GtCgjB+zorITeOOUTmiH5p7p44paz8AxUVBAuc7R2mhP/x8nRUp9JW63PNFz1J5QBQ==