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
- 57eb41f4e6eb9ed03b84c61e19e9c968bdbd9b96809d93d2a773cef797d9825f
- request
- b7a0cce4f29e2a9714a1b861931405a68be43629fafe042cb6229869d221724d
- transaction
- 662311a4036200bf9d2b21336de728b5c0852f3b6a48cb6cbff41e2f3add475bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12367
the chainentry 12367
- sealed to the entry before
- 2c6ca48aba32255c300fd79187eceea1af3f7b4a6ccc723b268eec01a29beffb
- this leaf
- d706d3dc10539d1701efba9425db98119d801521cb4b464259f2c1a2477f695c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- y3ApAHKgE5eXP8eGOCtpxoFETnfIseg5DbRz6plAXwDyaTOnOzKWzYRPuHBT5IUlNcEyQ43e++3zfoxArDwEDw==