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
- 2b0ed432cc8929d669d89f17420686bb47ed14e17256643e4d965a3b2feed167
- request
- 40dc110227abee22230b355b23722136b40554236ddf92d57ef14652ec45e4ee
- transaction
- 9897fa8287e9fd77ccf07c4cf01c67bee5edb2af290799b47636e53c0a97118ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3069
the chainentry 3069
- sealed to the entry before
- 10c90c14687247a7595f283a4949de7ed292b8cb9cecc426a1c33e161f448853
- this leaf
- c921fd3a4e32cd4b860e5b907efa1795e5c77a1d9f5457ebb6530e4208e032e6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0XA8znDSHGRlV6YGFoetR5Iwp8tRrD5PLlP5i+RbT6Zl2j04UzUivUtnQkK4uhXty6Bkvr83+BloDyMHmN+OAA==