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 |
|---|---|---|
REST API key → Read | Required | Read orders and refunds using the dedicated key.The linked WordPress user's access still applies. |
Write / Read-Write | Not requested | Revient does not edit WooCommerce orders. |
WordPress administrator password | Not requested | Use a consumer key and secret, not an account password. |
Choose Read even if another provider tutorial demonstrates Read/Write. The current connector uses the WooCommerce wc/v3 API, not the legacy API.
Create a read key and connect
Keep the key result open until the connection is saved.
Open the REST API key screen
WordPress → WooCommerce → Settings → Advanced → REST API
- Choose Add key or Create an API key.
You should seeThe key-details form opens.Choose the user and Read permission
WooCommerce → Key details
- Name the key Revient. Select an authorised user with order access.
- Set Permissions to Read, then generate the key.
Provider screenshotProvider reference: the Permissions dropdown is on the key-details form. Choose Read.WooCommerce: API key setup, with screenshots ↗ You should seeWooCommerce displays a consumer key and consumer secret.Keep both generated values
WooCommerce → generated API key
- Copy both values before leaving this page. Keep the secret private.
You should seeThe key and secret belong to the same dedicated connection.Complete the Revient form
Revient → Integrations → WooCommerce / WordPress → Connect WooCommerce
- Enter the Store URL, Consumer key and Consumer secret.
- Use the website base address, including its installation subdirectory if applicable. Do not append /wp-admin or /wp-json/wc/v3.
- Select Connect WooCommerce.
You should seeThe store appears in connection management, or a specific error is shown.Check the connection and one order
Revient → Manage WooCommerce
- Select Check connection, then Sync now.
- Supply the confirmed LOST payment-provider dispute, then compare the linked order's ID, currency, total and refund evidence on the case.
- For a chargeback, add the actual dispute record from the payment provider. A completed order alone does not establish a dispute.
You should seeAn order alone does not create a recovery case. Supply a confirmed LOST dispute; incomplete confirmed losses appear in Cases as Needs information.
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 billing first/last name, email and phone, shipping address, and the order customer ID. A guest order can have order-time contact fields without a linked account.
- 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 URL | The public HTTPS base address of this WordPress installation. | https://shop.example.com |
| Consumer key | The key-generation result in WooCommerce. | ck_… (paste the full value) |
| Consumer secretKeep private | The same key-generation result; it is shown only once. | cs_… (paste the full value) |
If something goes wrong
401 or authentication failed
Check that the complete key and secret match, the key has not been revoked, and its WordPress user can access orders.
404 on the API
Check the installation URL and non-Plain permalinks. Your host or site developer should verify that /wp-json/wc/v3/orders is reachable with authorised credentials.
HTML response, redirect or firewall block
Ask your site administrator to inspect the security plugin, proxy and REST API rules. Use the final public HTTPS store URL rather than an address that redirects.
Common questions
What evidence does WooCommerce supply?
Orders, refunds and shipping, including a tracking number when the order has one. Card authorisation letters and the lost dispute are not in WooCommerce. Add those from the payment provider. Only a confirmed lost dispute becomes a case.
Do I also connect WordPress separately?
No. WooCommerce and WordPress share this connector for a WooCommerce shop.
Do I need the legacy REST API plugin?
No. Revient uses the current wc/v3 REST API.
How do I replace a lost secret?
Generate a new dedicated Read key, use Reconnect for the same Revient store, and revoke the old key after the new connection passes its check.
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.