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
- 27ee9e1a20c16e9a1128f4b29f96fe260f7e0729dd9f3054bf42ad5a964c8672
- request
- 6dfeed45cc9870d5ff54caf674d482ada491864ef95e9d956280d22efdc137ec
- transaction
- 8ef8703d962cb9fce04f3e1f580a1483fb7cdc900e00354539de8e9139bb16a9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18498
the chainentry 18498
- sealed to the entry before
- 3d38df71e5632f04493b53b6ff98c89a658a94a69dcbbaa0b272109f2d0b8c83
- this leaf
- f32231b5910c67909e89c62b0b73d2b62a4cae13cf2868512dea02028a0ce268
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PRNA15Q2HTbd7LEyHJKMsiqloFIxBN7GWbaBnNex4Z/rECPst8vALzx5+KrrKWKoKE/gIKzfD4FOTlO9FvjaAA==