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
- d1cea4f470222193a03c95119ce02a67f82f6f416490cb43205085760c30de90
- request
- 0e7f1fa08ed1cbc3c618ba6fb0ca093b2010123ce2357401298f9586e33bb816
- transaction
- 98c3f639486e53ce42fe6033c9b3598ecaff87de327b6a08e22a5f29e9dca326computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73209
the chainentry 73209
- sealed to the entry before
- e28e799dade0716de1dde5de0f4af2e15567ad73573bdb92d53dd665a5b8623c
- this leaf
- 6a23e956742c8a08e59a4feb8038a222e106620775f86fd8a7b9276b45a88540
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iY2i4fMCTy0K6js8cSmZBQubIXC0uYB86OdrwDap8BSnbXuLo6pJkRegrS/NPcD+U2n1sdbLMMogWNNC+QqoAA==