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
- 65fce8748f36c31477268950c3991cfb3d7bdb8899bf1bb5686321d7e14b6861
- request
- 4c52203684bce9c210fa479bf3d7035a5641eb7bd8c51bc1942b92ba8e72ae35
- transaction
- 98339ace078efb13e377ebe1f0b5129febeeb38f30a36e9c21c82fb3f68ceb89computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10540
the chainentry 10540
- sealed to the entry before
- b34faffb3c1ce92b099e06e2b2b806c72ad888b3b0cbad783105f1021777271c
- this leaf
- 2b7171717e2ccf9be7f2471fea333cf6da60d6041bfc767e0f173b07c629ec08
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vfynIQFMhQC1eTtZQi4MxflC/QDeZid215Zs5NZ+LFvo3ZavyngCYfUBDFoxSlSE59qFj+1PjF+EcJd+UTjaAw==