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
- e48ad2e9fc4504b766661b3fb8d22d23dceb38f17d377dc35305307192acceb8
- request
- 66b5736b586aeebe2ab2e16cacc1273e536f39a201a377db265b1ef2116fed8b
- transaction
- 12c22a0ac4019d185815c6a69761c3e992470395619f9bd67a20b2b994f09a33computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20055
the chainentry 20055
- sealed to the entry before
- 3c8b0e8e2bca8307d66e977937ee7e228e20c9e9ddfccacb763cf4cbd4221eaf
- this leaf
- a967087cb48cb9ed5855e84c0d35521310b8b208cc7835f637128de586c8c198
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LzrWYDKRMFgAA3TFca8Tt2DNlyn5wbQBtU7oe7161T2hrYX5vPnhjnm0JNschNoP37XY9pfmO55sXpn7ba/9AA==