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
- b9f8087819391e420329f605af2d68f89de5a459a5e45c4e70bcd949411fa95a
- request
- 6cfe8613ec178a1992d747dd9c0ae8901f92fa4edf2a19ba967fa809d5a4e578
- transaction
- da8816b3aacc44c5ea2d97103eaa9fc26fe8833abebe17e906eb9a127c6c16f5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38253
the chainentry 38253
- sealed to the entry before
- 911bb5a39317feb65b911b1198ad02a14cf82a33518199d570591d80416e7f6e
- this leaf
- 243b1964b1ecd4631d7d194b9dbf9e4781b3660535d88c5aa530fe4269208363
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XVbz8ZDFArLPywVOMyfFn46x5SdU5WyRXUKEdV2FRJfan9HYUlhVG4osYkzZq8OxkCTGT/fDzL50xQdS0iDoAA==