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
- c69168ee6e31d09f3f5ab842027097edf6eebbc4c3bb519ab51cf540b227d58a
- request
- 280736d6d99c356dd8ca9db45deb77e69bd8c890a476f6a8cbda66c1ce92600a
- transaction
- b022fff6c66eb7a3767f730175c927a3dbd56ba5b31ace57cd6c5872437d7a6ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61312
the chainentry 61312
- sealed to the entry before
- 53fe5e61327efd60b7944295f0bf710c3d1c271abb06f0174f231aa3151952c9
- this leaf
- a2130a332401a83a71ab7cb1ba66eda1fcbdaae34048f3f66c41ad191979f70d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L9WTTIT1NuPlGk0tV3yfoPT4MXvE4/1tVOyf9t0giNAY4BGzsXn1gYzDrBZxFYE/6JFIHGm9IVCLSgJv98gzAg==