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
- 28d516f1f7fe8b7a1650ae3bbb47a749843063c0631a38908ea9795c527c2b4f
- request
- 8f39806ef19275c57aaf0d5d5d7ca9406a5a1a1cb51023efe88ca47fbbf608c4
- transaction
- f05ad4a442a7e8481a75d1b4106ab48bc403466150db341a8d0441e20057a393computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40338
the chainentry 40338
- sealed to the entry before
- 73655f955b0a799756df40ee78ca3661c05f9bad709e97c5ae4f5f75e87e26cc
- this leaf
- 06b232bcd470f64806c9043b597d3fbfab37a36f009996798d48ce4f497ea4bb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cGgThx+as/dEP+1RS/J40S/XxJTIfXXl+TrelTr9khzhOuLKe2tgJhhYVTzxSo//9MmVSsK63fGD1LAF4gzmDQ==