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
- b4766fcbf40e2d5d6bd1fe79c1f358acac9f9295e2cd1d34065cd1841fea6f84
- request
- d08d8888fa21b68a1107117c1b26ab779d898388a527d991392dcd8a77424437
- transaction
- 93e5744a81de13353c793bc86990eaf45d9523a0ea2b146d15d4301b9884f4a4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32769
the chainentry 32769
- sealed to the entry before
- 9a5f017cff92dde229ecd0765b888481ba3744e56a6b2437fe1627db957d6ddb
- this leaf
- 6fdeb8c75e27b6dd51771a3bcc8e01e9a05105c595e54aa79c034a299d3bb2f2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ktnHv12RsQPzC0FuGgEqtKeXY50FZ4XfqsMVl8mQOgwhgU/B+akHxUxNh5XhoBolCqhK1noHAVtLd45rSSVsBQ==