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
- 123305dfe03544cca58a1a044668530bdfbd9147312f97205ce68da71655c90f
- request
- 076cdb258f6d32edd4ab5edc7e55d5ea12416a94c26be87dcee283154ec17949
- transaction
- fbc610bd16c618c4f14c3c0990b736ef880c04288fd4726140da2b9cf0c9a353computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22603
the chainentry 22603
- sealed to the entry before
- f491c790c27816f2b1779defa62d61556c8dfcc1a07a2e3f31bbc2af6f92a64b
- this leaf
- e233380efbcf2faa0f3cbc98ab3ce25a3ba1fc86520ab334fcf9716700f25da7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NrwwraDiBAbyRCvhZe6wH623GE/89n/qPDhv6OgGA4XtjS8EDs0G7qBbAdWrs0+J89lxW2LCU89A4QOEsFBzCQ==