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
- a49c6a5bf41f932992ab0d53a7fd2891b01d185828b71ab91264687a1940e1e4
- request
- cb7cd196586f3ca73fff106dab8f943781eb02a39c63837e0f9be5386b2e9efa
- transaction
- eef30733bd10d063191237096fd268df75b825c18e63d6ee3b24b30cea00f9adcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70670
the chainentry 70670
- sealed to the entry before
- 2169c06a18e06b3cdad086550ea3475283f1ecd8283af9c13626e74972d433b9
- this leaf
- c61b26d30040c67f6523976fb6cfd90d12e99694790c1317e17253e8359369b9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +3o6zVeZvzxL0Mp85hJfXeI1eirlVW6l15wpmt/3/h8EfLHW4ZqU2a/n6hVV5AC8eoL1KW3KUnMy1Tu/rpD8Bg==