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
- 5d374e1c01a1a88a06a94e991845819f54700576ec297f5322e1b75a81081988
- request
- 4a7b1da4ee8a415ee8a391e122d6c309eff82b59194471e77f11a9fc4e306820
- transaction
- d20d18567c73bf7dca32ec321330e016e7db9de53d3c7195f16685866f60b4d4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74597
the chainentry 74597
- sealed to the entry before
- 9fae9c371697e176e91d62a4b5682028b3bfcd5d28aed5e3b9945dccb308e475
- this leaf
- ebb5b16323da554d8fe1ebe88c656130eb76fbb740017d4e78c42968ee105412
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VhfI5sGlxPlf/BIxx1+rJjWHMmM6wLA6xLD8CBXp9DlRbe07n9iZna/pGA0dyzJpQwBerbVBlnBgOI+fYlHNBA==