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
- f4cbc71cbd7f3e3c17dc536559fa5c2801b27f5d37a768237297dc7aa625c644
- request
- fe5a7a682454af76fb4948042ea5de020c00419be32b4edd473c29ed2a23f069
- transaction
- defeca372585c1105d042509d9ebacc0f79861a512814eef20ca39e552f1a1b2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1890
the chainentry 1890
- sealed to the entry before
- 1a88531c60bf22b68a59b764bcdaa2f6568528fa9a68b9e392f7a7b59ab5b645
- this leaf
- 26a3eabdd7265dbbb4a679e7b7b929327fc8c58a63597f4dc95f4f2f090065b5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1sPEOJXzTbieReWuixUmKfniFSnmg3oTawkAdziOHJjrklq6oUA1XHTEbqTAJFBhZz1gqKmCyR9Vxk5JFINLAg==