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
- ff412ddc66037f4219311abdcaac38dee7edaa3ed4cf7b3876097fb91e502716
- request
- ded72b1bc5d19f2559bdd2ef63751db14c963570f49e3a6d617510f861bc2d33
- transaction
- 29f7b4d1dd39c0e68de3e961d4dd72785cabe155e7f95ededeb9af14e2142eadcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16139
the chainentry 16139
- sealed to the entry before
- 1cb7e993e4cf2462d2f614f072a1997db99bf36a3253c1daaeccf0c2eba972f2
- this leaf
- 7bb9fd8e70f2da06f8442e37ea7805ab6640ccd3561a71419226be4a139becd8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GoBnpENYdXOpFPn0AkAG3+VRcojRapCvYzVVuuseyQsbUWUA3kvq0WfZtPBxpJuifh7Fq/Ge13CKsZ0RSuMEBA==