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
- 5abf974b1117720c9e055501b20285feea2735320d1fd32f50bb25afd22ee48d
- request
- bd84b2a72cc1147341831cb25e2ed74abd78dc928e377d8378eafd2b118669e1
- transaction
- c7dae2877c8f48404305e5b998759874a7dbfd35e6523025d3c1f0bae57bbe79computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54944
the chainentry 54944
- sealed to the entry before
- d32f1a4d30db280196dea666dbbd5dcd4ba7c48b005eede60b6e6d6efcf4e8ec
- this leaf
- 4ac020888bd05d13f5ffda4be9f6e1ee1a48fb30f05502a6bdde6104c7f2aeb4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YRObhbvvYaiLHbt/ib0WuiOHKs5pJEAIF62/8BqLR9ANvpYARa/WciynyRgxKfptEKYrgujbl1UEaxAUHczDAg==