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
- 2e30fa58d5cb8036b6706826ed7dff59dbf0e06ddee8904287c2c874acc04468
- request
- 90532c3986116d46d949b57905c0d05e77f52ab7d85f464fe601675e24bc5a98
- transaction
- 336ba6889c599eadf55550ea1e1680346a3fda51cb76cbe64673c19494bb37c1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57627
the chainentry 57627
- sealed to the entry before
- cb8abb575c0489b19f469ae71f8b70d308fc47c2489ff9569a40ece83407c391
- this leaf
- 60100471b44dac797609916df17ea9f51225ce3a6c26290725e1606e4b7ea551
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hfao4fX6hLsvA7pbKrNPmd2plZrPcy8FUZHDMZNSLNQ06WwdfkBlrDmRd+466hWVw7/9F85qd1eOZSDUdgV+BA==