Update index.md

src/pages/resources/progress-messages/index.md

@@ -81,7 +81,7 @@ Examples:
 
 The most common way to respond to a message request, is through request hydration and the jobs endpoint.  By simply providing a header that contains the appropriate envelope_id ("x-cardsavr-envelope-id": "<GUID>"), responses become simple account updates.  Note that credential responses aren't always username/password (although that's most common).  The [merchant site endpoint](https://swch.github.io/slate/#merchant-sites) defines the necessary values for each merchant site. (e.g. "pin" or "email")
 
-Endpoint:  PUT /messages/place\_card\_on\_single\_site\_jobs/:job\_id
+Endpoint:  PUT /place\_card\_on\_single\_site\_jobs/:job\_id
 
 ```json
 {
@@ -104,6 +104,20 @@ or for TFA responses:
 }
 ```
 
+The other mechanism is to post directly to the messaging endpoint for tfa responses:
+
+Endpoint:  POST /messages/place\_card\_on\_single\_site\_jobs/job\_id:/credential\_responses
+
+```json
+{
+  "job_id": 101
+  "envelope_id": <ENVELOPE_ID>,
+  "message": "1234"
+}
+```
+This method is not recommended for new credentials since the account needs to be updated regardless.
+
+
 All the SDKs provide simple interfaces for ensuring the correct data is returned in the response.  There are also sample tests that walk through how to attach envelope_ids in responses.
 
 #### Querying messages by cardholder