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
- 2a7a18206d8946974c205d4a26b95f5f10b763a569536425dc397653b1297ae2
- request
- d43491f202f5263f530c2d4c68cc5ec47e1df6eda4b6d2cecc5481a828215368
- transaction
- e58acdc85e1fcb8cdab58747493bbf0de3d3ac719caf55c7067d2d6fed2a590ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2100
the chainentry 2100
- sealed to the entry before
- de8832ce9d80f07e3ad26969591a5201318b17dfbddb6c97058ab741a837eab6
- this leaf
- 16b47f068175dfc64581438a0498cdfc8bc3efa61fa546d67049cfe3f579e1c7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FYOYbMJrFme+hS3QegO6tdfogomVK5oUU7RJjXzJ8Dx/OpRBifezzps5IW3HqwExo6rBWwdaAuCqSVPGi0mPDQ==