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
- fe74f79213a2498ff21da4fb852deb737269120d347b6ff239ba9a88780ee73d
- request
- 29b9ad4151835354db5ed3b62814cc2e11efb911f1e322093074408f32856e3f
- transaction
- f49bbd4b857d79d3128677d26c1079498502ba00265bc4c2e67f8ce910069dd7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72844
the chainentry 72844
- sealed to the entry before
- ba8bb3c8164e86e3796b5672fdef4dabc4c6df97954f51bdf286f1a3841fb79b
- this leaf
- 3112349c800289b8d785d84facbb50be3256e45389dd91adf668354f565497ae
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- I6SddMXDs24jbB/Acrg/jsyAig+evA8rrAHZw7M1jpL9zofnIBCjGp6wq7OclAuEA6aERcEuweItZQr7i9SxAw==