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
- 617dbec97b9723979fd428c929e2047ef9f7035844f07873e724651c75198a92
- request
- b221dfd8df0fb79241972a38c1537639670a25d12dc818839b702d57d0d291c5
- transaction
- ee02d00f45037db17b92c7cc7ef20b6031c3414fe25baae5cdb7a975c9e08debcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11153
the chainentry 11153
- sealed to the entry before
- f09492b841df34b37b99b63e0210fe21b9bda86df06491befc005c13cf9f0954
- this leaf
- 265b5bd227bc9a925ea60179abf7e84c0b664852352326b50c4680213ae5b752
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RR4hN7/t1D4x/H4jMXYt84Zdn9DcZ+SGRHQHAmjceKINrZ+ONj4Qoi+/JJ7zR4nT25mRUZdhdgVH2fFGKwzKAA==