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
- 3e0b99195f03dca475cf50d4e3b5229bbae8570a0b59025ac92864669b86d884
- request
- 4cce33367a927527e3a991017ad81b4ab3abdb459f1324533e6b4aec79578bf3
- transaction
- dcd75d87e1f5a9172444ee62ffd85542d988827f912eccf8c71eb73b9ccde625computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24237
the chainentry 24237
- sealed to the entry before
- 07221e833d64b27e1c35f70c27bf30b2117e1c258532bbd5261e676eecd7c85a
- this leaf
- 6792db7b1ae45aab28df0bb96ff31b2547783d18596e67865543ba28ca133700
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 45+ow7LOPyM3erVY8LMkeCLz6Sw/bTYtli7rd91oxavZ7KjyHR+Jp4bLFvbxbpxwEzeB9SqAtJDy8mb6B3W3Dg==