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
- 205f3f2a373c7e67d7efb2745c1fc61c35f6cb18069b712af69b0c87deafdf2e
- request
- 2eb74728dfd91e325118ed3d080f1a88d87b28c48661b853cad4c721ad30c78d
- transaction
- c3e817aa90b9a557d1d21362f436a57aed62554e0f11ed6a562c2a5e2372f3b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50037
the chainentry 50037
- sealed to the entry before
- 7104d4aad0d7ef60414d48b77edf11bd1d1f2e03f83885ba24114a3f9ef961b5
- this leaf
- 5ab74b7b091a4b112e48d6ed479fc6a274851ee63ce63794bc279e46cd4bd270
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 27R1Rb4wyCFpjV3CAogR1/DfgZmasJzheVYIsA3vBZ5wXIq2ZZQrPE/UvTfOUytqgTC+hKM1z2ouhkRQHIDjAw==