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
- a92b2853c4c5217e63217f8cbc0c38b3dab05cb1f4ff37dd276c905b0915b443
- request
- b64ebef4e14db87d70d37bd88259436288d89a191797261e88c42c755343d1ac
- transaction
- 78c8f7252903fba2347a1f649f6d834ad0a1d46609f9486887bf6deb0297d499computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52094
the chainentry 52094
- sealed to the entry before
- fae51b3326256b2b3373a853a2395e4248b87dad99a5140ace3fa54bc93f8f9d
- this leaf
- 930ac1b80dfc55da9c6010e904e0724ad26c8a6dc9e99898edc6e9124b8227c0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oIrK2Co6ak52dtTxLDmQCZQnPPkt2EnnN+tOXaV0HyAZoBHockB3lTcaVGI8lNI+EHCV75nxI3/pEgHJS5NBCg==