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
- 79de146d89ef97b2e4bf24310cf5b2fff1cd7b693f2f362e67df98d993947093
- request
- eab2d8761978a74be80dd682287b8438b1a5da6459b5519d94b32fb902ed8231
- transaction
- 4b2fe16f19abd208a9a20219886e6caac7c876e10f108e6ad975d06aed186a9acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40764
the chainentry 40764
- sealed to the entry before
- 329cc2b91deb9aa532360868e747d30974d4217f7bb55581cc8bded3dda711b6
- this leaf
- f7921c27266337a8e7a6f1e723657a889d8f89f3f3d1c021c039d58b66067a33
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lCA3Sk46FXtNbx/6YoAKIE/4X2IMuaU8aGHtaf/KY/BadADYmvBMwVOPJPEv8uThEHYJAgOg7+kDAlxuCBlnDA==