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
- eacb269b2b5a03bac0d93a1790e7513b2870ff72b950b242dd963c0be2a077ea
- request
- 4cddbd2f7803bf392164b5a2e01436c63a44982b4dcc2e37c44628d008e2606d
- transaction
- bdeb074fe8b3ac5f746746b2b96555d0ff5b0dbe90ebc609a24dc60c2b30882dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67592
the chainentry 67592
- sealed to the entry before
- fe13cfd84ce19bde59be2dd2b04f4b27a403abe4a917fd24fcebebc92be5c3af
- this leaf
- 0da7ba9e87c2694d20ec802512a766a92e1af796e6f861592ea070575935a48a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Mg1j2PPc9gODbL1b5aegQCaFoYo+GTGR14e52QmjDMl2QtfPKwOjCTxDGLz3UQ33kfzwKDDkNchUqHIIzN1GAw==