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
- 3d95caf1fd5e91991b69043f8b0485f13983b40491797c31a4d7fd4da5656aec
- request
- eed3e6da8e5a2a1e37d70fd9e8a07e4142728d5bbd48dc02de72fa79eb52441e
- transaction
- e894b63715535b4ea39e42efcc06d4c6ad57073c81728c568f69ffa2d5920bfccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63575
the chainentry 63575
- sealed to the entry before
- 3ebd67b45befa005f54efb6ef2d282ed99937f2ee8bee111a0857bd866db8e61
- this leaf
- ede71dbaf6aea922d807be0c59db3166a5efd3d27a7dc6898e268fb56a69b895
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- APajK0o7AFGz7m4PzcsA8x/29VkgyMLP0cBG82SEgVeMvKJQ/LmiZiZQ5zgRWmvMUbYLgVEZH6f9Vbv0H8NwAg==