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
- 15cb791e68157aeaa02c5be539e8cff8d0f8f1f5f33665187bbfb2abec123e88
- request
- 384ec1174d92f5983177a70866c267e111846b8db1c1ecec8434c73c7bb7b0fb
- transaction
- d270d8b5eff5ce02ee2435cf1375267055f5d685add84953417ad500731dda35computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11485
the chainentry 11485
- sealed to the entry before
- 1b87668813d238f4cbc6da833822e5b9bcc59c830bfbba7332c4432449ce7d82
- this leaf
- 7ae5a07cbd32a49603df7e5b66e99d22d989ad02b19f9f2848ef144a1d15c275
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- goqJsBwkjGYxOESip3GuE1aUmZpY5FB1o5M1V6V89IIpAAaslQs0N8l4MIGm9FK8XV2z+Faes1m2lhFNY172BQ==