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
- 9458a1ffe1628677ff5f00145a720d5c65b72f9b741c5f3cd994440873145364
- request
- df8003721d9864aec22bc1bd87bca9aeade45bba1c289c346b7a013418ed6202
- transaction
- 0f567f359a22a68dd71fe1a07c2e2231d88ba0a964febf4481f6ac34708943d2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21033
the chainentry 21033
- sealed to the entry before
- 44e17ced767fa9cb444d7c287634781bd32bbb8f50b192847613b788b456bb23
- this leaf
- 546932d22c7164c0b7446c47a44a19b27459849b558346fbdfdbefbb15e9f79d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ax2by4AYtSev/Ml9lB/GvoXcgRqPAyuOCASdH8CxzKstxsdPLDwoCB/5vzgur2OywAsoQGX0XgkzwurMERMhCg==