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
- 35eb51aa91b0dcbd59f52e41a1693e8fabfa700b257e7edee0d9e1b81ee61459
- request
- 4c55936a908a8219912e9f302e5fc7cef180c438feb089ac7c0c48375ea236e9
- transaction
- a236651a0719829ee694cd4081c5997ae8cdabc3fcf04f615e8c39973a673b54computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 471
the chainentry 471
- sealed to the entry before
- 5d4efb63d37b5d35efd62f520e13642d990dbba378f74c72909565c14ddd5f8e
- this leaf
- 3762723e28875eb5f90ecf7c68ff057f5396a7bda7c0e13b26b20725fb993267
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a9IVXaHztMWgprbHHUeO+9wxL3GSdBZNu7wElHe122DbNFD6UOnJK8Hvxbb6eyShmpN00Xzndfugy/SJgxFeDg==