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
- a54b416e39dbd15100efd9ba2fc11e37ea782e38790711ba4f8ccc405fb94727
- request
- 5f393dd6d7a402782de64ad267c78998dd0e314e33be7dc995018073a99bd28d
- transaction
- bf88d169d40c0f77bac26618e035a805599f53ac3b2be1b07da4431e41fe22aecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68927
the chainentry 68927
- sealed to the entry before
- 47d9c8188846bd1f344606cc670df3bf39ea4ab6e7c526421f8289a2fcaeac81
- this leaf
- ece1e01b4f7ae8feb7a5d385778daaab813f5a21a10ede7e7e12387b1603e55d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BuK620AA3bGZOaoxTzyqWyeFwucnwA30mfgZTlDfLkvkxfuU83+0OA9DV8ywdADlnmsZByH9VAcLut36WjSoDw==