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
- 3c77a496e0b20ad706d7e49e5fd33a5155eb132cfb8a7343036d701fd6460c5d
- request
- 26b32672910092425fd73623513c879813b9bb12afd698e9812d2d86e2406fe4
- transaction
- f9f4bfc73a2134c80a6fdea751d7d2ed975aa7a40dff49cd30546e00baf4532ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 766
the chainentry 766
- sealed to the entry before
- 339fc81b9a54c61b87e5471bb05751e949d89e48d4c75269008db5bec4cbc851
- this leaf
- 4239132568a02a93a6835eaa850245308de4db7547fc783bcbcd2360e6d80926
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FyrbMm29QX4sbhCrfhyUCI3eoGfh89aQ1g9tVsr2u/mS80/RNt1IpBl+O3yVwRvxLONTM2ziYVait9JpOk67Cg==