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
- fd0fb71ba06423ae9185ae9856eede461ed254e012cbedeac253173cc0c551c5
- request
- b0f20d96b5079b5545092d4a503bac972a7a03fab9adf1877af16c40d7bb81c6
- transaction
- ab26b94d5b766548c9f811090df6b30e5db693e7a6073b41352b70ca42b6870ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29581
the chainentry 29581
- sealed to the entry before
- 73aea79b332f51859c3a291ab70cf542bee783831a0bdb36dcedfd2c540b6909
- this leaf
- 239436ce7976e43a5fd7d00925d999d27d1fb31cd63bd7b39b9df31be236bd01
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dmjbEgVQ2k3XXDbW4ZnBQxW4fI/Z6d1ZNUQ/i0Uj87zm2OgpiaSQd/IK9EmnVQ2SWvIRieRMhmZVVDtSeFSeAQ==