diff --git a/src/pages/graphql/payment-methods/payflow-pro-vault.md b/src/pages/graphql/payment-methods/payflow-pro-vault.md
index d3e25be57..65d49e00d 100644
--- a/src/pages/graphql/payment-methods/payflow-pro-vault.md
+++ b/src/pages/graphql/payment-methods/payflow-pro-vault.md
@@ -18,6 +18,8 @@ The following conditions must be true to use this payment method:
You cannot use this payment method if the customer decides to use a credit or debit card that is not stored in the vault.
+PayPal PayFlow Pro transaction IDs (PNREFs) are valid for use in Reference Transactions for a fixed period of 12 months. Once expired, the saved card will no longer be displayed and must be added again.
+
If the customer's stored payment information becomes outdated, use the [deletePaymentToken mutation](../schema/checkout/mutations/delete-payment-token.md) to remove the token. Then perform the actions described in the [PayPal Payflow Pro payment method](../payment-methods/payflow-pro.md) to generate a new token and process the order.
diff --git a/src/pages/graphql/schema/b2b/company/queries/company.md b/src/pages/graphql/schema/b2b/company/queries/company.md
index 66cc5639b..408a0259f 100644
--- a/src/pages/graphql/schema/b2b/company/queries/company.md
+++ b/src/pages/graphql/schema/b2b/company/queries/company.md
@@ -115,6 +115,7 @@ query{
firstname
lastname
email
+ id
}
... on CompanyTeam {
name
@@ -143,7 +144,8 @@ query{
"__typename": "Customer",
"firstname": "Taina",
"lastname": "Garofalo",
- "email": "donadmin@example.com"
+ "email": "donadmin@example.com",
+ "id": "Ng=="
}
},
{
@@ -159,7 +161,8 @@ query{
"__typename": "Customer",
"firstname": "B",
"lastname": "BB",
- "email": "bbb@example.com"
+ "email": "bbb@example.com",
+ "id": "Nw=="
}
},
{
@@ -175,7 +178,8 @@ query{
"__typename": "Customer",
"firstname": "A",
"lastname": "AA",
- "email": "aa@example.com"
+ "email": "aa@example.com",
+ "id": "NQ=="
}
},
{
@@ -191,7 +195,8 @@ query{
"__typename": "Customer",
"firstname": "C",
"lastname": "CC",
- "email": "ccc@example.com"
+ "email": "ccc@example.com",
+ "id": "NQ=="
}
}
]
diff --git a/src/pages/graphql/schema/cart/mutations/place-order.md b/src/pages/graphql/schema/cart/mutations/place-order.md
index d23cd3e30..a23373b9b 100644
--- a/src/pages/graphql/schema/cart/mutations/place-order.md
+++ b/src/pages/graphql/schema/cart/mutations/place-order.md
@@ -16,6 +16,8 @@ Perform the following actions before using the `placeOrder` mutation:
- Set the payment method
- For guest customers, assign an email to the cart
+As of Commerce 2.4.9, the `PlaceOrderOutput` object contains the errors available on the top of the response node. This assures easy error control and provides compatibility with older versions.
+
As of Commerce 2.4.7, the `PlaceOrderOutput` object can contain `orderV2`, which provides full details about the order. When the mutation runs, Commerce generates and returns a token in the `orderV2.token` field. You can supply the token value to the [`guestOrderByToken` query](../../orders/queries/guest-order-by-token.md) to retrieve details about an order created by a guest shopper.
@@ -53,10 +55,6 @@ mutation {
number
token
}
- errors {
- message
- code
- }
}
}
```
@@ -70,8 +68,7 @@ mutation {
"orderV2": {
"number": "000000006",
"token": "0:3:OSScWU6PKLn3kFyMhNWyskG0opgVvFBnJmtuaFHKGwDFT83S6Kv9U39iYwixuU+vhwDz2AF4pCs3GtLhHbQ="
- },
- "errors": []
+ }
}
}
}