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
- 69fff8719ef0f36568c4ba5e2213b2d2e17bd8ffb76ee188ebe2387b65faa638
- request
- 2da383ccd385f575281decd62cccfd36108b78a92b2a6460c3d8a02429141bd2
- transaction
- 1dd1cfaca46042a453d00048379c812c3b4bd41fb494806c37903ca21ee7ddcccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70675
the chainentry 70675
- sealed to the entry before
- bcc127be27ea0a2e45ee63bbf45b9ee1165d635d2b5c98a8c7edfc803365f085
- this leaf
- 9862b7066e08cfb1b0d86e5241521f17c7a6b919ebcdb0dcd35c15731ee85665
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4S7T4t82D907AADPx+rtx9cVDpmI/Zb8axUKu7Z9sAk+TXS0jXKlcvbkS+FLcraCMsPQ22JbzGW9lZYU9WRQDg==