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
- d00ccf2bdd9bc2f94cf4029dc7989a55c611405f94b01322c097d97aff96aab6
- request
- 5bc12c942bf5d223c6a1ffcafc78ba5620af73c937c1ed7245ac2e8e459aca49
- transaction
- 7e56d264be93652da004ee49a383dbfdeb1958fe546d2fe07d287f5ab618229acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9074
the chainentry 9074
- sealed to the entry before
- 382000658ea38b9d0bb45c2b1eee9dc44e91c87cde24288c7dd702831e78233e
- this leaf
- 2b89487ada02a3102bb5bb5bbea251feaf26e0303ed77f1b9c148383758a412b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tN+5KCCWYhtu1o+dXVYEcbWqsoVAReZoTz4WN1iIF9alMeNG76oCGMwVk4xWmlnp4IsLmkXyunY7eNFNQ/kIAw==