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
- e21bb19f117d6d1825fc64094c3c0f673655045420d0501daf97ca2838ae08ac
- request
- b5974ebfe039b2121c6c1a0da68c43384323a7277a708c8c9f5e07416b269c2d
- transaction
- 6fc06268860f5d384ba9d0ac70babfe7e4161697c88f5da35350ab006bd2b0b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75045
the chainentry 75045
- sealed to the entry before
- 6487df92f4f70422b54780de15deaad565ccff107f5386d0c7ff3c8e637e9b22
- this leaf
- 52fac6c5464a29d23ab7a4abfd273d2d399426fe64eb83539adec7bfe267d803
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yWGRvyk2Iz7Dl645jN3rCykjOmVsyJwt02Y4dZna+YL8hbW2C6NW9tWKuO7FnJb5bFiDWcFQScuruOWtSyAtBw==