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
- 155a1af6ab759a5b96f761e47719f086279bd2d52d93fda200683fe390626034
- request
- 204c66ff33cb6d3385aeed78371beaa82d99207dfbbd56208bb42050e06dae7b
- transaction
- 9cb70bb435b08de5de0caacd9b479c02c8318b6cf1c17541c651fa52e264b966computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41723
the chainentry 41723
- sealed to the entry before
- e6d1981ff81bca4aa46900616e7474beb5fb65135085de3eb488749f924eaec5
- this leaf
- be56dfbda2ce5c51fc129c0c0ff390da36f6ca3f0daaf8de508449fb69e10cca
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- quo8HB3HlowEfYX/ZBwqRyU3NjEpO2szSKsmp9Uj8SA7ZiQaagjHkTXRJ0wvllE2thl5XVwpzTkLB2Zsma79AQ==