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
- 1cc3301940941663884b3a190429970620b615c3b2e9bf7e0358bb762f278577
- request
- 184a8dff3096bd225f7d64c14e87faa825f66eba917b13b73f121ac6c3485181
- transaction
- fcc26e2d446b7a536a9442348b8cc4ef85f473db188488d07dad41d30c6e7814computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53422
the chainentry 53422
- sealed to the entry before
- 9fb213ab583395f28b23b1c29181a937c2c4b7cd0049a49efed74e8b0595b343
- this leaf
- 841ad9bb9bd6cb73adc21e61150768fadbf11b9f4ac10f6aafea160e69699fba
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- S7paLzlO0gkLtcAyeM3cAxF0/hUiq+frkfmulNBiAJYpfVtVOn9k5BrvSLnOYeipSfUDrgMnWLDWu8EzCYa9Cg==