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
- 31242f0bbfe070cb3dcc92d1e69aafa0a28cea51edfafc5ba8b90e49011f85ce
- request
- ab70933915ecb237f56ca52ed8920d54babe228f332caaac765af766db79ea31
- transaction
- ddb5936ea5fb525fd02fb98229688a6c1f7aaf22ae05e9595ad30b941b95ab38computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24822
the chainentry 24822
- sealed to the entry before
- d83aceff173ba9a76927ee64c5b7f5cce2e394405ce10d482473bfaed5497179
- this leaf
- 3d6256c507c0b90868000eb964c545085feffb456debb617b0f494716bb19b73
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6xCtO0tv5J/X/6gItpSTI6HH8BVgMzlpncYRIYk5yy/Ekiml6ZtkGH8AMIDi3irl+PoTYeGfA2rJtzQvihgODg==