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
- 56c3c46434797f8bd4aff091d830aa1cefa1c8928d34e1a2141285350e3a901c
- request
- 28d6e80ad598984a9bdb37b8665e88282c265ff0af65b94238d1e1090efa220a
- transaction
- 2e2dd76ea399070f75a2cb00cbf2c87eab119d3e37a86cbb0d7279210dcbd0abcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29178
the chainentry 29178
- sealed to the entry before
- 27d042a88d94b226d5dc1d51b39e261fe8d4f80091321c1fd25208c7255fdf7e
- this leaf
- 40b55547669db8a6476bc99dc46e0f7e5974c736ffd90b3aa36e497e85dcce66
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- E5Emymu1T2tvSI+P6b+f8ax0uaJT7g+hJXDhCIrtYGirthhvnMFjXbyTpOOdB2utTbkPQpdB4RJjZR5PC23BAg==