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
- 02c19d40fa566eb9514a82fbec8e321d7c4b969749c648fdd90335e31dd8db8b
- request
- b2707457c6b3343839a83f8cc8a991833617556358f1c45e489718525aa933b8
- transaction
- 6fe4d9cae67e520b8571dc4676fe0b53c8ade609d4a5a1a6830d7aa8a23e5b9ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39870
the chainentry 39870
- sealed to the entry before
- e782e438e16503573982f6a7c2be39e78cde219262f3897adf53f8834d183a26
- this leaf
- 26352ed7c85d36d011d2adc45a26b7906d378f83c407f462fa0c586b3077eff1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VRgE38v1YEJomTMT2OrgSaViMHTdkjZK1wJh0trFLvZJCcqncW3PTAlBeWfvRWZL8utoH1UkQtkdfraaOzs+BA==