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
- b0e953b111cc571d72a4a487eaffa5ca855fd5806d2537593d815777106644a2
- request
- e0266edadfd4fed15dccee7a6458deaf71aa934e5327784686bca4a0976f50ac
- transaction
- eb4979a9e7101b2b0a916c0d15c14abda9aef4ab8e89617b93e227389a9615a5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11448
the chainentry 11448
- sealed to the entry before
- d5141392da22937fda253d87ffbbc4c475ca205180484e7cb442dc97f62c1602
- this leaf
- 8b895a1486335fa63467133862427411fa2c3c06483a30d00ce98ff7c6e60388
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Mykqy7JY5lBTgtLupEY3/eTQxW0ohDVIk/gPtzikAYk54oVFheFLA62/lNSZfWAhuzQSDyUSjSTZLrFGTgbnCw==