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
- 013f9a6819e8c45d823ced7c84548e880c9f14b4ac1c95cc44a11c1ed44bf426
- request
- 41290cb06b42f5f90e181ffb4187803258853c0f5e7f1b98f5e9427bdc13a4fa
- transaction
- cfe88afaeb34b742dc06e99dee24311f20b9c0574da31bb362edd349499cad3fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62928
the chainentry 62928
- sealed to the entry before
- 941510f9e30b21cf9081a9d4562c54a8ef88f8d471ac58110e1caa2b5daa5a6d
- this leaf
- 7c539f825d313be9dd036f8ef774226b04a4ea0a9bd3502dd81f77c61a132f5b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WO88eRPYjzyk7p2d3QESbw92t5DbbUINFbi0n9d51Ij0ArNk9ZWeYYG1AZZscVlYq3QHwSrHTmGDPxDmIk6HBw==