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
- 7e30ede08ebfcbdfcdd8fe77adeab68164960095426f9428f635d43e4e0f3402
- request
- db94d580f7561625dc7fe628e3432dd45b7b20cde701ba9b1bced9f705316e29
- transaction
- ca9fa60823a00954299d1e83e84e29377833b4f692f39dd57110a01f60f0633acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10692
the chainentry 10692
- sealed to the entry before
- 6cb1a7a3a7475d8cdefe4caa4fff1238d2b50fc7d2635964f49d8e2d2066a6bf
- this leaf
- 8c5ea430677a170577206635dabaff4567efab6093a7fafa0c8bf7ccc466fd70
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- H7JZFB9oJK9IrSmxpL98Fur5S/C+yEyKF13mn5990SaFFc0RwxJ9TeCaecPdOcCasHfn0CNkP7DxpcEEyYVEAA==