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
- 3d870f8eacbf5e905a43120787ba383b0c0ad654094f8eddcad620b1534d6432
- request
- e37ed64d73a0213711f13f1b1c6184a240349e06d3e198a5dcd794b371257b95
- transaction
- 1d8759bdae2c055fef9ebabae949ab84851e4ea6ff4487a7a3d6eb2782a555bfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39131
the chainentry 39131
- sealed to the entry before
- d716a17a77d9ddc12704c1e824385a1e77fd190f0d034d456b3f948ae9a7e3fe
- this leaf
- 46f17bbe4a3e416116641557f8e46c034ec213196d5abecb9bcf73d6d2f7db02
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Dg5zccp0LA3Tre9aQbX934uVoEqhRZIRArQ5WtCT2snWrbChagUkSipPPHV8kLapUFB6vUzZ86nfw6fd5YndBQ==