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
- 3d47e9f79ea85f1894fb95864cd3725faa912282726ced446b8b3f2727a5dcd6
- request
- 8b55538703061d7ecfdcee2f6696e89409e5f67b28fddb4b82431cd73a06e5a9
- transaction
- 1e0a1d5c421a60f84088c701cef4a61979c7ceefd3a4031b362adc1c7e6bc798computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52731
the chainentry 52731
- sealed to the entry before
- 754f4e60cc805df06888f3c1fc104b045173f737fdb5bac0055b5cf72bfc013f
- this leaf
- d4086b9f883e6c4cb8c33c67ec4603a7a5f2b7a8287f8d93ae381ba53193f045
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- I9mHiB0ilxID3RP/joFcifm1Itjvshys4ZzYyAm0MsHMyjb3CojhXtrbCBW+t2fQzsFyy49z4EaR/AgHvdEOAw==