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
- b6642ed1ae2ecff51b2f0f3382a68556c13cafd2024858bd9e92e440aedad982
- request
- 73d10dc14a1fb1508997ffcf86638ed0eb01b5c0ca3539c7f49ff0021b441360
- transaction
- e13e524e025084b19c341341f2ee8dd43553f80924586aadf590e55073cd60c1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3012
the chainentry 3012
- sealed to the entry before
- 4048aab11bcb23bbb88f4717baa056f3040db3336506ee8ee4ae8cee0a24ac01
- this leaf
- d1b083f869b02e3b4a9d74af9541af3154b2e661afd8f66ec966f201f6579e33
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kr+Pz37HoblOSpHXkhi37ExWzpZik579QjSTql1pK4r8jW8C0e6t+l5d+NFz/sQYoPIfQITOaN8K3bXJH/oeBA==