Add link to Cash App Pay event listener docs

afterpay · Dec 3, 2024 · c66a125 · c66a125
1 parent c8bab13
commit c66a125
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 5 deletions.
diff --git a/docs/getting-started/v2-with-cash-app-pay.md b/docs/getting-started/v2-with-cash-app-pay.md
@@ -101,7 +101,7 @@ cashAppPay.unregisterFromStateUpdates()
 
 ### States
 
-`CashAppPayState` is a sealed class. Some states are for information only, but most will drive the logic of your integration. The most critical states to handle are in the table below:
+`CashAppPayState` is a sealed class. Some states are for information only, but most will drive the logic of your integration. See [Cash App Pay SDK documentation][cash-app-event-listener]{:target="_blank"} for a complete list of states. The most critical states to handle are in the table below:
 
 | State  | Description |
 |:-------|:------------|
@@ -143,7 +143,7 @@ After retrieving the token from your server-to-server call, you must sign the or
 ``` kotlin
 Afterpay.signCashAppOrder(token) { cashAppData ->
   when (cashAppData) {
-    is CashAppSignOrderResult.Success -> TODO("Create the Pay Kit customemr request")
+    is CashAppSignOrderResult.Success -> TODO("Create the Pay Kit customer request")
     is CashAppSignOrderResult.Failure -> TODO("Display an error and restart payment flow")
   }
 }
@@ -154,7 +154,7 @@ Afterpay.signCashAppOrder(token) { cashAppData ->
 ``` kotlin
 Afterpay.signCashAppOrderAsync(token) { cashAppData ->
   when (cashAppData) {
-    is CashAppSignOrderResult.Success -> TODO("Create the Pay Kit customemr request")
+    is CashAppSignOrderResult.Success -> TODO("Create the Pay Kit customer request")
     is CashAppSignOrderResult.Failure -> TODO("Display an error and restart payment flow")
   }
 }
@@ -286,7 +286,7 @@ sequenceDiagram
 
   Afterpay API-->>Proxy Server: Capture Payment Response
 
-  Proxy Server-->>App: Capture Payment Respnse
+  Proxy Server-->>App: Capture Payment Response
 
   App->>App: Handle payment<br>capture response
 ```
@@ -299,3 +299,4 @@ sequenceDiagram
 [api-reference-props]: https://developers.afterpay.com/afterpay-online/reference/javascript-afterpayjs#redirect-method
 [cash-button-docs]: https://developers.cash.app/docs/api/technical-documentation/sdks/pay-kit/android-getting-started#cashapppaybutton
 [create-checkout-endpoint-docs]: https://developers.afterpay.com/afterpay-online/reference/create-checkout-1
+[cash-app-event-listener]: https://developers.cash.app/docs/api/technical-documentation/sdks/pay-kit/android-getting-started#states
diff --git a/docs/getting-started/v3-with-cash-app-pay.md b/docs/getting-started/v3-with-cash-app-pay.md
@@ -108,7 +108,7 @@ private fun initializeCashAppSDK() {
 
 ### States
 
-`CashAppPayState` is a sealed class. Some states are for information only, but most will drive the logic of your integration. The most critical states to handle are in the table below:
+`CashAppPayState` is a sealed class. Some states are for information only, but most will drive the logic of your integration. See [Cash App Pay SDK documentation][cash-app-event-listener]{:target="_blank"} for a complete list of states. The most critical states to handle are in the table below:
 
 | State  | Description |
 |:-------|:------------|
@@ -309,3 +309,4 @@ cashAppPay.unregisterFromStateUpdates()
 [intent-filter]: https://developer.android.com/training/app-links/deep-linking#adding-filters
 [custom-url-schemes]: https://developer.apple.com/documentation/xcode/defining-a-custom-url-scheme-for-your-app
 [sandbox-app]: https://developers.cash.app/docs/api/technical-documentation/sandbox/sandbox-app
+[cash-app-event-listener]: https://developers.cash.app/docs/api/technical-documentation/sdks/pay-kit/android-getting-started#states