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
- 065f719abf35ea84b9bb76b3eb4f6a95f9dc5532bf41e7946d207af6caa02158
- request
- 14bf78019d04cc6fdc57b458894f8591546a3b1a84f971febeb15fda8e2b2706
- transaction
- 449d7a77d44da7745f0a44fa7cb971318f53e04fe33e77bcb67d5fc5d9953aafcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36825
the chainentry 36825
- sealed to the entry before
- 4393ab592f2166795f82563b3ccea7f4d739081ea1b0b28260c35dad631b8301
- this leaf
- f3a3c915662bfc64bde9b313ac4cf279e45a2dcc11b1d29c0abea06f445daa4f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D3BFfJTGewvMJYf7rfJq6SkdWfAH/SoREx8vTej8ky130dLHeAqsiFTNWQGPfA9AUgIVoH6g9oFCrfOoqh0kBA==