Consistency changes and cleanup for PTC docs

Author: runa-pc

features/pay-to-card/introduction.mdx

@@ -17,7 +17,7 @@ Pay to Card facilitates instant transfers to other accounts, powering use cases
 
 Retrieve the Pay to Card products using the [product list endpoint](/reference/2024-02-05/endpoint/products/list). You can identify these products by the `payout_type` field, which will be set to `payment`. Each Pay to Card product supports a specific currency and country. You can refer to the [product listing guide](/features/product-catalog) for more information on this endpoint.
 
-```json title="Pay to Card product example, fields truncated to for brevity" icon="file" expandable
+```json title="Pay to Card product example, fields truncated for brevity" icon="file" expandable
 {
   "code": "P2C-US",
   "name": "Pay To Card US",
@@ -33,7 +33,7 @@ Retrieve the Pay to Card products using the [product list endpoint](/reference/2
 
 To make an order for a payment you simply specify the Pay to Card product code for the currency and country you wish to send funds in.
 
-For our example we will be using the `P2C-US` product code for a $10 payment to a recipient. The payment will be sent to the recipient's email address via the `EMAIL` distribution method.
+For our example, we will be using the `P2C-US` product code for a $10 payment to a recipient. The payment will be sent to the recipient's email address via the `EMAIL` distribution method.
 
 ```http title="Example pay to card order" icon="globe" expandable
 POST https://api.runa.io/v2/order
@@ -75,7 +75,7 @@ Refer to the [order endpoint reference](/reference/2024-02-05/endpoint/orders/cr
 <img className="block dark:hidden" src="/assets/graphics/p2c-flow-light.png" />
 <img className="hidden dark:block" src="/assets/graphics/p2c-flow-dark.png" />
 
-When a recipient opens the payment they will be guided through the following flow on their first redemption:
+When a recipient opens the payment link, they will be guided through the following flow on their first redemption:
 
 1. Enter their email address to authenticate
 2. Securely enter their card details
@@ -87,7 +87,7 @@ For a returning recipient, they will only need to enter their email address to a
 
 <CardGroup cols="2">
   <Card title="Testing" icon="flask" href="/features/pay-to-card/testing">
-    Test out the pay to card redemption jouney in our playground environment.
+    Test out the pay to card redemption journey in our playground environment.
   </Card>
   <Card title="Support" icon="circle-info" href="/features/pay-to-card/support">
     Read through the potential failure scenarios and suggested resolution for

features/pay-to-card/support.mdx

@@ -1,66 +1,51 @@
 ---
 title: "Support"
-description: "Potential errors scenarios for Pay to Card and their resolution."
+description: "Potential error scenarios for Pay to Card and their resolution."
 icon: "circle-info"
 ---
 
 We've categorized potential errors into three distinct areas, and for each, we've developed specific contingency plans and operational procedures.
 
-### 👤 User errors
+## Recipient errors
 
-These are errors that can be self-corrected by recipients
+These are errors that can be self-corrected by your recipients.
 
-#### Payment details
+### Payment details
 
 1. Issue with the card number
-   - User will see the error message: The card number you have entered is incorrect.
+   - Recipient will see the error message: `The card number you have entered is incorrect.`
 2. Card is unsupported
-   - User will see the error message: The card you have entered is not supported. Please use a Visa or Mastercard debit card.
+   - Recipient will see the error message: `The card you have entered is not supported. Please use a Visa or Mastercard debit card.`
 
-#### Returning user
 
-1. Returning user lands on the first page but has already redeemed the balance.
-   - User will see the error message: You have already redeemed the balance.
+## Order errors
 
-### 🖥️ Order errors
+These are the errors that will require your input to resolve
 
-These are faults that will require your input to resolve
-
-#### Insufficient funds
-
-1. Insufficient balance at order time
-   - If your account has insufficient balance you will be unable to create the order for the payment. The API response with a 400 status code, the error message body will contain the type `insufficient_funds`. Check the [order endpoint reference](/reference/2024-02-05/endpoint/orders/create) for more information.
-
-#### User ineligible
+### Recipient ineligible
 
 1. Payments cannot be sent to anyone under 18 years old.
-   - User will see the error message: We cannot send funds to anyone under the age of 18.
+   - Recipient will see the error message: `We cannot send funds to anyone under the age of 18.`
 2. Payments cannot be sent to anyone who appears on a sanctions list.
-   - User will see the error message: There's been an unexpected issue, please contact the issuer of this link.
+   - Recipient will see the error message: `There's been an unexpected issue, please contact the issuer of this link.`
    - Runa will send you an email to inform you that this has happened, with our reasoning attached.
 3. Card issue
-   - Payment sent to a user who doesn't have an eligible debit card with Visa/Mastercard.
-   - User will see the error message: We can only send funds to a Visa or Mastercard debit card.
-
-### ⚙️ Processing errors
-
-#### In-journey errors
-
-1. Authentication error: Recipient hasn't received email with code
-   - User will need to contact Runa for us to investigate what might have gone wrong with authentication.
-2. Authentication error: Code that recipient has received not working.
-   - User will need to contact Runa for us to investigate what might have gone wrong with authentication.
-3. Card issue: The recipient's saved card has expired.
-   - User will see the error message: "Card expired" and will be able to contact Runa for us to delete their original card so they can add a new one.
-   - _Note: from early April recipients will be able to self-serve editing their existing cards_
-4. Card issue: The recipient's saved card has expired.
-   - User will see the error message: "Card expired" and will be able to contact Runa for us to delete their original card so they can add a new one.
-   - _Note: from early April recipients will be able to self-serve editing their existing cards_
-5. Fraud Suspected
-   - If fraud is suspected, we will hold on sending out the payout until we have established that the payment isn't fraudulent. During this time, we will either ask the end recipient to share additional information, or we will have to cancel the payment and inform you that it's been cancelled with a reason as to why.
-6. Recipient bank has rejected payment
-   - The most common payment issue we are likely to experience is the recipient's bank rejecting the payment we send them. If this happens we will send the recipient an email to say their bank has rejected the payment, with advice to either resolve this with their bank or to contact us to manually delete their card so they can try a different card.
-
-### All other issues
+   - Payment sent to a Recipient who doesn't have an eligible debit card with Visa/Mastercard.
+   - Recipient will see the error message: `We can only send funds to a Visa or Mastercard debit card.`
+
+In these cases, we recommend cancelling the payout link by logging into your Runa portal. Please use an alternate payout mechanism to tranfer the funds to your recipient.
+
+## Processing errors
+
+### In-journey errors
+
+1. Authentication error: Recipient hasn't received email with code, or the code is not working
+   - Recipient will need to contact Runa for us to investigate what might have gone wrong with authentication.
+2. Fraud Suspected
+   - If fraud is suspected, we will hold on sending out the payout until we have established that the payment is genuine. During this time, we will either ask the end recipient to share additional information, or we will have to cancel the payment and inform you that it's been cancelled with a reason as to why.
+3. Recipient bank has rejected payment
+   - The most common payment issue we are likely to experience is the recipient's bank rejecting the payment we send them. If this happens, we will send the recipient an email to say their bank has rejected the payment, with advice to either resolve this with their bank or try a different card.
+
+## All other issues
 
 Your point of contact for any other issues: support@runa.io

features/pay-to-card/testing.mdx

@@ -19,17 +19,17 @@ Here's a high level summary of the Pay to Card redemption journey:
 You're able to walk through each step of the journey in the playground environment.
 
 <Info>
-  **Delivery of links for orders is disabled in the playground environment by
+  **Email delivery of links for orders is disabled in the playground environment by
   default**
-  <br />
-  Every distribution method will still return a link in the `payout.url` field
+
+  Every order via API will always return a link in the `payout.url` field
   that you can use to access the redemption journey. See the [playground
   reference](/docs/playground) for more information.
 </Info>
 
 ## Testing the redemption journey
 
-After placing the order, you can access the redemption journey by following the link in the `payout.url` field.
+After placing the order, you can access the redemption journey by following the link in the `payout.url` field of the API response.
 
 ### Email verification
 
@@ -43,7 +43,7 @@ You can test both successful and error cases by trying scenarios such as:
 ### Billing address and card details
 
 <Warning>
-  Never enter your actual address or card details on playground links.
+  Never enter your real address or card details on playground links.
 </Warning>
 
 There is no billing address validation in the Playground environment, so you can use any dummy address.
@@ -60,7 +60,7 @@ The playground environment only works with a specific set of cards. Use the foll
 
 2. Card details for validation error
 
-   Following should immediately trigger a warning for incorrect card number
+   Any incrrect card should immediately trigger an error (example below):
 
    Card Number: `4111 1111 1111 1112`
 
@@ -70,7 +70,7 @@ The playground environment only works with a specific set of cards. Use the foll
 
 A returning user will already have their card and other details saved.
 
-To simulate a returning recipient flow in the Playground environment, append `+repeat` to the username part of your email address.
+To simulate a returning recipient experience in the Playground environment, append `+repeat` to the username part of your email address.
 
 For example, if your email is `user.name@mailserver.com`, use `user.name+repeat@mailserver.com`.