Before you start
Ticks are kept in this browser only.
Follow the path that matches your account. Provider screenshots come from the linked official documentation and may show a different theme or older navigation. Configuration examples are labelled separately.
Permissions to choose
Use these exact permission names. Conditional permissions are needed only for the features described.
| Permission / scope | When needed | What it allows |
|---|---|---|
Orders → Read-only | Required | Order and shipment records.Scope: store_v2_orders_read_only. |
Order Transactions → Read-only | Required | Payment transaction records for the selected order.Scope: store_v2_transactions_read_only. |
Modify, Create Payments and unrelated resource scopes | Not requested | Keep unneeded permissions at None; Revient does not edit store data or take payments. |
Store-level scopes cannot be changed after creation. If the two read permissions are wrong, create a replacement account and reconnect. Follow Revient's read-only table rather than broader permissions used in general developer tutorials.
Create store-level credentials
Use a separate API account so this connection can be rotated without changing other integrations.
Create a V2/V3 API account
BigCommerce → Settings → Store-level API accounts
- Choose Create API Account and V2/V3 API token.
- Name the account Revient.
You should seeThe form shows an API Path and a list of scopes.Set only the two read permissions
BigCommerce → Create API Account → OAuth scopes
- Set Orders and Order Transactions to Read-only. Leave unrelated resource permissions at None.
You should seeThe account grants order and transaction reads without modification access.Save and copy the correct two values
BigCommerce → API Path and saved credentials
- Copy the store hash from the API Path, then save the account.
- Keep the Access Token from the credentials result or downloaded file before closing it. Revient does not use the Client ID or Client Secret fields.
You should seeYou have the store hash and matching access token.Connect BigCommerce in Revient
Revient → Integrations → BigCommerce → Connect BigCommerce
- Paste the Store hash and API access token into their corresponding fields.
- Select Connect BigCommerce.
You should seeThe saved connection identifies this store. Each additional store needs its own credentials.Verify orders and transaction access
Revient → Manage BigCommerce
- Select Check connection, then Sync now.
- Supply the confirmed LOST payment-provider dispute, then compare the linked order's ID, total, currency, payment references and refund evidence on the case.
- If the payment provider holds the chargeback, import its dispute record separately.
You should seeAvailable source records are visible. Checking the connection alone does not confirm every transaction or dispute fact.
Review the collected evidence
Check the source facts and processing result after completing the provider-specific connection steps.
Check the case and automatic evidence results
Revient → Integrations → Intake, then Cases → Evidence
- Compare order-time billing contact, customer ID and each shipment's delivery address. Check transaction/refund access separately from order access.
- Shopify intake accepts only CHARGEBACK disputes with final status LOST and a verified remaining disputed balance. Inquiries, won and open outcomes are excluded before customer enrichment, tracking, scoring and AI.
- Confirmed lost chargebacks with missing facts appear in Cases as Needs information. Missing facts remain unknown until supported by evidence.
- Historical non-qualifying records remain in internal audit history, outside merchant intake and active Cases.
- Cases combines retained Test and ordinary records. A small Test badge identifies records that cannot be routed, sold or counted in live financial totals. AI still requires its approved configuration and valid permissions.
- For each outbound, replacement or return parcel, check the tracking number, event dates and item coverage. Registration requires a confirmed lost dispute and verified notification-disabled settings. Delivery photos and signatures are separate private assets; unavailable assets are labelled, and a recipient postcode does not prove the delivery address.
- Use the row menu for one case. Select at least two checkboxes to show bulk actions. Refresh evidence requests current connected-source data and then checks it; Recheck stored evidence uses the facts already retained. Follow each row's progress and refusal reason.
- Archive retains history and may be blocked by active obligations. Use the Archived filter to restore a case. Reimporting its source does not restore it.
You should seeYou can identify the current evidence, unknown fields, processing state and next merchant action without losing historical assessments.
Match these fields in Revient
Enter your own account’s values. Example values are for orientation; do not paste them as credentials.
| Revient field | Where to find it | Example / guidance |
|---|---|---|
| Store hash | The API Path: the value after /stores/ and before /v3/ or /v2/. | abc123xyz |
| API access tokenKeep private | The credentials result after saving the API account, or its downloaded credentials file. | Paste the full Access Token |
If something goes wrong
401 or invalid token
Use the Access Token, not Client ID or Client Secret. Check that it belongs to this store hash and has not been revoked.
403 on orders or transactions
Review both read permissions. Create a replacement API account if its scopes are wrong, then reconnect the existing store.
Store hash rejected
Copy just the alphanumeric segment of the API Path; remove the URL, slashes and store- prefix.
Common questions
What evidence does BigCommerce supply?
Orders, order transactions, shipments and refunds on those records. An authorisation result is used only when the transaction payload contains it. The lost chargeback still comes from the payment provider.
Can I reuse one token for different stores?
No. This connection uses credentials scoped to one store.
Do I need a callback URL?
No. This store-token connection does not redirect you through an OAuth approval screen.
Will this grant access to chargebacks held by my payment provider?
Not automatically. Order transactions can supply payment references, while the actual dispute may need a separate provider export.
What is the difference between Refresh evidence and Recheck stored evidence?
Refresh evidence queues new reads from available connected sources and already selected mailbox messages, then tracking and reassessment. Recheck stored evidence reassesses the retained facts without claiming a new provider read. Existing findings stay visible until the work finishes; unavailable sources and partial refusals are reported for each case.
Which disputes receive recovery scoring?
Shopify intake accepts only CHARGEBACK disputes with final status LOST and a verified remaining disputed balance. Inquiries, won and open outcomes are excluded before customer enrichment, tracking, scoring and AI. Historical non-qualifying records remain in internal audit history, outside merchant intake and active Cases. An order or tracking number alone does not establish a lost dispute. Supply the actual confirmed loss and preserve its original order and dispute identities.
Will testing send messages or release a case?
Evidence-testing mode blocks customer, agency and buyer delivery. Importing records or reviewing an assessment does not release a case.
What happens when I disconnect?
New reads stop and the Revient connection is disabled. Evidence already retained remains subject to the workspace retention and removal controls. Revoke the application or key in the provider account as well if you want to remove its access there.
Source documentation
Use these provider pages if a menu name has moved or your plan shows different options.