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
- 4b311da56df720904a25156ccc8c7a542a6e0e16407efd13887b4616627961d9
- request
- 202e81f0f80af01d506cee6aae71dd904aed4bc4e8a970be1bc1f3da2437d2f9
- transaction
- f1f314cbe993e3d02bda6155fa3ee67f9e7ca718608557649cb4fcb5a4140f40computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50640
the chainentry 50640
- sealed to the entry before
- 79bf881fcd4887a3d8b69fe3472f968c2704b7620a4dc21cc227d4d00de79d18
- this leaf
- 7f11f27541b7aec5afa58840a8c781c0bc3ebb1d3ee50c0e2c8320049b5dd8c0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZMqF92mM0gLfbIwIVlJj5SIu/3DfDE2oDDkitoRViBljWCfORiQT3awdq1AQsLUW0t94Wg7darDjdeMYj5jxBg==