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
- 7cd0befb04feea89d1f7d1411bd76f0d877bbe44c915d2e46970d83ed684246f
- request
- e4472dbd77bc4aec2d6ca02a9fcb9ac60030a77421685199dfedba720cdd0ff3
- transaction
- a719bf1f79846d481a747bbc61cf1e41331fa3a51740a3a4b24aff2c9544968dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48468
the chainentry 48468
- sealed to the entry before
- ff5cf1a416c70cd8f4f612f1b054d8bb44ebb96343ad78a7569a7e9cee152642
- this leaf
- 63b8b9478fb5d2007b5de45db3b332065d35d008543ef0564ab3e26468d09987
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hqa7dQAtz0Q4bKBQuMCIN7zsdO9nN4C758eNbsxC3w12RUriMlhS8Pdl7UcExrF6FbqdA5HbpIXnpmr0U+OkDg==