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
- e14dfbbe74a0bf6752608cffb4b3432939f6aa2750d3c9b50e32a3c43dcdec6a
- request
- 3b8c43baae4e72144f0127b2a5cfe36766df98edf5429dc87b689fc985d064fa
- transaction
- 419f820117dea9d385790570602024f7bf144925f762d3da4b351b7912185d49computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56306
the chainentry 56306
- sealed to the entry before
- 8c0caf9b61e30ca2cc1d52a054a716bca98599cf9cdcc0627f159495d21938c7
- this leaf
- edab40391526aa17b1328f2bd31b9fb887cbb76702aa5d36fa273742156be104
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2mkUbymOd/mlA7EcdVLT068nTAULaOuO7W0bLJBkDNe3jBC5sU3tfTPvHJ8JdxZH1rYCMtMgbMCWhMxMlJXVDw==