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
- 227123118583ef70a2b01c5a0c8559eb01b8a2c286378a4f028cea56d18c3826
- request
- 4402aafb05cb3a17c9330c26ea6f0b4cb80bccd5e2c184d20e631b95ee19eeee
- transaction
- e4e349244a9c6d7255efce762d51333dce435b57670d1a55bf625db9f39c0328computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63946
the chainentry 63946
- sealed to the entry before
- ccb08c9c0c98ed82eee9214ade6e47952306506ba8bd15c27d5bd5bc9da5b009
- this leaf
- 2d0241bf24c5365233620279ee1a4342dd113307503083143c5d95f2aa140de9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9UAvGV7xW7SVoK35EIYNKNCqhUoaoLRDAwekZlAtmzL9bHz/aaW48Osvl1TWDUva73VYRATi1XPq0667T8q3CQ==