diff --git a/docs/concepts/connections.mdx b/docs/concepts/connections.mdx
index b978289..5601642 100644
--- a/docs/concepts/connections.mdx
+++ b/docs/concepts/connections.mdx
@@ -35,7 +35,7 @@ The connection contains several important pieces of information.
## Remove a Connection
-At any given time, you can [remove a connection](/api/delete-connection) as either the seller or the merchant relationship in the connection. You can do this from within the [Credova Portal](https://portal.credova.com/connections) or as an API call:
+At any given time, you can [remove a connection](/api/delete-connection) as either the seller or the merchant relationship in the connection. You can do this from within the [PublicSquare Portal](https://portal.publicsquare.com/connections) or as an API call:
```shell showLineNumbers
curl -L -X DELETE 'https://api.credova.com/connections/conn_73t7igFxDZvN9hypi7yoPwbxy' \
diff --git a/docs/concepts/webhooks.mdx b/docs/concepts/webhooks.mdx
index 357c1a7..04edaae 100644
--- a/docs/concepts/webhooks.mdx
+++ b/docs/concepts/webhooks.mdx
@@ -2,7 +2,7 @@ import { Alert } from "@site/src/components/shared/Alert";
# Webhooks
-Webhooks provide asynchronous notifications from the Credova platform to your system. These are important for events around onboarding, connections, and settlements where an event may happen in the Credova platform and your system needs to be notified so it can take action.
+Webhooks provide asynchronous notifications from the PublicSquare platform to your system. These are important for events around onboarding, connections, and settlements where an event may happen in the PublicSquare platform and your system needs to be notified so it can take action.
## Webhook Request
@@ -36,14 +36,14 @@ The key parts of the webhook request are:
|---------------|--------------------------------------------------------------------------------------------------|
| `id` | This is the ID of the event and can be used to retrieve the [event by ID](/api/get-event-by-id). |
| `environment` | The account environment where the event was triggered. |
-| `event_type` | This is the event in the Credova platform that triggered the webhook notification. |
+| `event_type` | This is the event in the PublicSquare platform that triggered the webhook notification. |
| `entity_id` | The ID for the entity. |
| `entity_type` | The entity type. |
| `entity` | The current instance of the entity at the time of the notification. |
## Event Types
-Credova publishes several events which can be subscribed to via webhooks:
+PublicSquare publishes several events which can be subscribed to via webhooks:
| Event Type | Description |
|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
@@ -53,15 +53,15 @@ Credova publishes several events which can be subscribed to via webhooks:
| `onboarding:merchant:update` | This event publishes the Account entity when the merchant onboarding status changes. |
| `onboarding:seller:update` | This event publishes the Account entity when the seller onboarding status changes. |
-
Credova always publishes the current instance of the entity in the webhook notification.
+
PublicSquare always publishes the current instance of the entity in the webhook notification.
## Notification Delivery Attempts
-Credova will attempt to deliver a notification once an hour, for up to 24 hours. Credova requires a `2XX` status code response from the registered endpoint to mark the webhook notification as being successfully delivered.
+PublicSquare will attempt to deliver a notification once an hour, for up to 24 hours. PublicSquare requires a `2XX` status code response from the registered endpoint to mark the webhook notification as being successfully delivered.
-When the webhook notification has been successfully delivered, Credova will mark the Webhook Event status as `delivered`. If the number of delivery attempts has been exhausted, the Webhook Event will be marked as `failed`.
+When the webhook notification has been successfully delivered, PublicSquare will mark the Webhook Event status as `delivered`. If the number of delivery attempts has been exhausted, the Webhook Event will be marked as `failed`.
-Webhook Events can be viewed from the [Webhook page](https://portal.credova.com/developers/webhooks) in the Credova Portal or cam be [retrieved from the API](/api/get-all-webhook-events) for the Webhook.
+Webhook Events can be viewed from the [Webhook page](https://portal.publicsquare.com/developers/webhooks) in the PublicSquare Portal or cam be [retrieved from the API](/api/get-all-webhook-events) for the Webhook.
The Webhook Event will contain information about the last delivery attempt:
@@ -120,7 +120,7 @@ In order to verify the signature, you will need to get the `key` from your Webho
}
```
-Using this key, we verify the signature passed by Credova:
+Using this key, we verify the signature passed by PublicSquare:
```csharp showLineNumbers
// Gets the signature from the request header
diff --git a/docs/guides/marketplaces/onboard-sellers.mdx b/docs/guides/marketplaces/onboard-sellers.mdx
index 8a3a782..938bbb2 100644
--- a/docs/guides/marketplaces/onboard-sellers.mdx
+++ b/docs/guides/marketplaces/onboard-sellers.mdx
@@ -10,15 +10,15 @@ In this guide, we will walk through the process to invite and onboard a seller f
sequenceDiagram
actor se as Seller
participant mk as Marketplace
- participant cr as Credova
+ participant pq as PublicSquare
se ->> mk: Start seller onboarding
mk ->> cr: Create seller invitation
cr -->> mk: Seller invitation
mk -->> se: Returns seller invitation link
- se ->> cr: Seller navigates to invitation URL
- cr ->> cr: Seller accepts invitation
- cr ->> cr: Seller completes onboarding form
+ se ->> pq: Seller navigates to invitation URL
+ cr ->> pq: Seller accepts invitation
+ cr ->> pq: Seller completes onboarding form
cr -->> mk: Redirect seller to success URL
mk -->> se: Complete seller onboarding
```
@@ -29,7 +29,7 @@ sequenceDiagram
### Get your Secret Key
-Next you will need your `Secret Key`. [Go to your Developers section](https://portal.credova.com/developers/api-keys) and click `Reveal` for your `Secret Key` and copy the value.
+Next you will need your `Secret Key`. [Go to your Developers section](https://portal.publicsquare.com/developers/api-keys) and click `Reveal` for your `Secret Key` and copy the value.
Save the Secret Key as it will be used in the next steps of this guide.
@@ -61,7 +61,7 @@ The connection invitation should contain an `invitation_url` where we will send
"account_name": "Test Company, LLC",
"status": "pending",
//highlight-next-line
- "invitation_url": "https://portal.credova.com/connections/invitations/invt_41vV8UVXrEgpT5AWYr2ry4SKN?merchant_name=Test%20Company",
+ "invitation_url": "https://portal.publicsquare.com/connections/invitations/invt_41vV8UVXrEgpT5AWYr2ry4SKN?merchant_name=Test%20Company",
"created_at": "2024-06-30T01:02:29.212Z",
"modified_at": "2024-06-30T01:02:29.212Z",
"success_url": "https://merchantwebsite.com/success",
@@ -83,7 +83,7 @@ This will create a [Connection](/concepts/connections) between your Marketplace
-Once the Seller has completed their onboarding, Credova will redirect the seller back to the `success_url` provided when creating the invitation.
+Once the Seller has completed their onboarding, PublicSquare will redirect the seller back to the `success_url` provided when creating the invitation.
## Getting the Connection
@@ -143,7 +143,7 @@ curl -L 'https://api.credova.com/webhooks' \
This webhook will notify us whenever a connection invitation is accepted, when the seller's status has changed due to completing onboarding, or when either the seller or merchant has removed the connection.
-Webhooks are a great way to keep your system in sync with Credova.
+Webhooks are a great way to keep your system in sync with PublicSquare.
## Conclusion
diff --git a/docs/guides/merchants/collect-cards.mdx b/docs/guides/merchants/collect-cards.mdx
index a3bb8a0..81459b0 100644
--- a/docs/guides/merchants/collect-cards.mdx
+++ b/docs/guides/merchants/collect-cards.mdx
@@ -7,7 +7,7 @@ import ConfigureElementsSection from "@site/src/components/docs/_configure-eleme
# Collect Cards
-In this guide, we will set up Credova Elements SDKs to capture cards in a frontend application and securely authorize and store the cardholder data while avoiding PCI requirements.
+In this guide, we will set up PublicSquare Elements SDKs to capture cards in a frontend application and securely authorize and store the cardholder data while avoiding PCI requirements.
## Getting Started
@@ -15,11 +15,11 @@ In this guide, we will set up Credova Elements SDKs to capture cards in a fronte
### Get your Publishable Key
-Next you will need your `Publishable Key`. [Go to your Developers section](https://portal.credova.com/developers/api-keys) and click `Reveal` for your `Publishable Key` and copy the value.
+Next you will need your `Publishable Key`. [Go to your Developers section](https://portal.publicsquare.com/developers/api-keys) and click `Reveal` for your `Publishable Key` and copy the value.
