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
- 632f9a6e8584a55bdd4e73a8648992c939408a054128506c041ba8a515814da5
- request
- 0fa6ae0986096937ca7fc39d012d75411cdab8492c78cc38df5df076a10195ce
- transaction
- 2fc66402c47ae8a1a97cc0ea24f360969ca8963514b0587ef3e5ffa3403b53dbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63049
the chainentry 63049
- sealed to the entry before
- 9296c9b121242261c2b8d606f75e38eda1835d0c70d5c1bc63ef002a7ddf322e
- this leaf
- bf24fd6af6e24ed7069aa156aa30cb59895393c546391dc3d084ba32d07bbd45
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zExccDZEd/qOdPP+1gjsoRkp6QGm1reCfAhHkg2eNojS2qioz1D6wExaajNF9ejNx752JxrofKZGDSR4Io4AAQ==