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
- 6511af1eaed086ba13e71a972eda3b4573104dc4f13fcafb1f69d0145edfe957
- request
- 95427e302ab84d42cdffbdf69cb6508e89288a37455e516b51d08cd5f55cb355
- transaction
- d94c3a20fca865850506263243799ec7c6b952df3dd2aceb72cb7237d09ad3e5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53722
the chainentry 53722
- sealed to the entry before
- 2de6a131d0ca9f2b78382b32661b83eca52635e308e976b3130fe820d60f93f0
- this leaf
- 3e6a0009da13ce5aa5d501903b877d08f2d0b375d3abe4e01b31d3b0d73723e9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6KYTWVvXDHkPiGzynxVNRhND+YO90NWQptPLxWmNnLxsBKdwRRF1Lb/ZAi5gJGHqcCOK2Dwz/s65ymjkairxAA==