Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| | Partner support email | Required | Email | Used by BigCommerce to contact tax provider, in the case we need to forward a merchant support request. | `support@sampletax.example.com` | | ||
| | Links displayed in the control panel | Optional | URL, Title, Description | Link(s) displayed to merchants when they navigate to **Settings > Setup > Tax > _TaxProviderName_**. One or multiple links supported. | `support.sampletax.com`, `Sample Tax Support`, `The Sample Tax Support website.` | | ||
| | Transaction type | Required | Production, Test | Whether your tax provider will be handling production traffic or conducting test transactions. | `Production` | | ||
| | Partner support email | Required | Email | Used by BigCommerce to contact tax provider, in the case we need to forward a merchant support request or discuss integration improvements. | `support@sampletax.example.com` | |
There was a problem hiding this comment.
Hard to read sentence (confidence: 4/7) retext-readability retext-readability
| ### Test tax provider (optional) | ||
|
|
||
| Additionally, when providing the details for a sandbox tax provider configuration, it's unnecessary to specify the below properties because they are inherited from the primary production tax provider configuration (all other properties are still required): | ||
| Tax providers may choose to build a tax provider instance that supports test transactions. This test tax provider instance will sit alongside a primary production tax provider instance, servicing merchant-facing use cases, or to support the tax provider's own development processes. |
There was a problem hiding this comment.
Hard to read sentence (confidence: 5/7) retext-readability retext-readability
| * Tax provider visibility | ||
| * Platform availability, i.e. all stores or only specified store hashes | ||
| * Supported / unsupported countries | ||
| Tax providers that support test transactions have lower expectations than those supporting production traffic (e.g. timeouts, error handling), and so it is important to differentiate between a production tax provider and a test tax provider when sharing provider details with BigCommerce. |
There was a problem hiding this comment.
Hard to read sentence (confidence: 5/7) retext-readability retext-readability
|
|
||
| <Callout type="info"> | ||
| We recommend tax providers request to create only one sandbox tax provider within their production tax provider configuration, any development procedures related to testing different estimate, commit, adjust and void Tax Provider API endpoints should be performed externally and decoupled from the BigCommerce platform to avoid unnecessary dependencies. | ||
| We recommend tax providers request to create only one test tax provider. Any development procedures related to testing the tax provider's different estimate, commit, adjust and void Tax Provider API endpoints should be performed externally and decoupled from the BigCommerce platform to avoid unnecessary dependencies. |
There was a problem hiding this comment.
Hard to read sentence (confidence: 5/7) retext-readability retext-readability
| Offering an account login flow within the tax provider's app iFrame will commonly be required to capture these basic authentication credentials from merchants. An account registration flow may also be helpful for offering merchants the ability to create a new tax provider account. Learn more about designing the app UI [here](/docs/integrations/apps/guide/ui). | ||
|
|
||
| In either case, the [Update Connection](/docs/rest-contracts/tax-app-connection#update-a-connection) endpoint should be called after the tax provider's app has been successfully installed. Tax providers will need to include `store_hash`, `provider_id`, and `X-Auth-Token`(`access_token`) values. | ||
| In either case, the [Update Connection](/docs/rest-contracts/tax-app-connection#update-a-connection) endpoint should be called after the tax provider's app has been successfully installed and the merchant's account credentials have been authenticated. Tax providers will need to include `store_hash`, `provider_id`, and `X-Auth-Token`(`access_token`) values. |
There was a problem hiding this comment.
Hard to read sentence (confidence: 4/7) retext-readability retext-readability
| ## Configure tax provider settings in the control panel | ||
|
|
||
| Once you have successfully installed the tax provider's app and provided basic authentication credentials through the Update a Connection request, merchants can enable the tax provider on all test stores supplied by the tax provider in [sharing provider details with BigCommerce](#sharing-provider-details-with-bigcommerce). | ||
| Once you have successfully installed the tax provider's app and provided basic authentication credentials through the [Update Connection](/docs/rest-contracts/tax-app-connection#update-a-connection) request, merchants will be able to adjust the tax provider's settings to activate supported functions on their store. |
There was a problem hiding this comment.
Hard to read sentence (confidence: 5/7) retext-readability retext-readability
| The tax provider's settings screen can be found by navigating to **Settings > Setup > Tax > _TaxProviderName_** in the control panel. | ||
|
|
||
| If document submission is supported, navigate to the provider's settings menu, found at **Settings > Setup > Tax > _TaxProviderName_** in the control panel and ensure the **Submit Order Data** checkbox is checked. | ||
| To enable the tax provider to respond to tax estimate requests, the merchant must choose which supported countries or subdivisions the tax provider will fulfill tax quotes for. |
There was a problem hiding this comment.
Hard to read sentence (confidence: 4/7) retext-readability retext-readability
<!-- Ticket number or summary of work -->
# No ticket: issue templates
## What changed?
<!-- Provide a bulleted list in the present tense -->
* add issue template config and bug report template
## Release notes draft
<!-- Provide an entry for the release notes using simple, conversational
language. Don't be too technical. Explain how the change will benefit
the merchant and link to the feature.
Examples:
* The newly-released [X feature] is now available to use. Now, you’ll be
able to [perform Y action].
* We're happy to announce [X feature], which can help you [perform Y
action].
* [X feature] helps you to create [Y response] using the [Z query
parameter]. Now, you can deliver [ex, localized shopping experiences for
your customers].
* Fixed a bug in the [X endpoint]. Now the [Y field] will appear when
you click [Z option]. -->
## Anything else?
<!-- Add related PRs, salient notes, additional ticket numbers, etc. -->
ping {names}
<!-- Ticket number or summary of work --> # [repo] Issue templates, rename directory ## What changed? <!-- Provide a bulleted list in the present tense --> * Issue templates, rename directory ## Release notes draft <!-- Provide an entry for the release notes using simple, conversational language. Don't be too technical. Explain how the change will benefit the merchant and link to the feature. Examples: * The newly-released [X feature] is now available to use. Now, you’ll be able to [perform Y action]. * We're happy to announce [X feature], which can help you [perform Y action]. * [X feature] helps you to create [Y response] using the [Z query parameter]. Now, you can deliver [ex, localized shopping experiences for your customers]. * Fixed a bug in the [X endpoint]. Now the [Y field] will appear when you click [Z option]. --> * TBD ## Anything else? <!-- Add related PRs, salient notes, additional ticket numbers, etc. --> * #3 ping {names}
1 participant
No description provided.