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 |
|---|---|---|
Magento_Sales::actions_view - Orders → Actions → View | Required | Allows the current connector to list and read orders, including their recorded refund totals.In the standard Magento 2.4.8 permission tree: Sales → Operations → Orders → Actions → View. Your developer should check the installed version's route ACL if labels or permissions differ. |
Magento_Sales::shipment - Shipments | Required | Allows Revient to read shipment dates and tracking references.Sales → Operations → Shipments. This provider ACL also covers some shipment write endpoints; the credential itself is not guaranteed to be read-only. Revient uses GET requests for this connector. |
Invoices, Credit Memos, Customers, Catalog and All resources | Not requested | The current connector reads order refund totals and shipments; it does not call invoice or credit-memo endpoints. Do not grant unrelated resources for this setup. |
These are resource ACLs, not Shopify-style scope strings. Shipment access can authorise more than reading at the provider level. Revient's connector only reads sales data; use a dedicated credential and the narrowest available resources.
Create and connect your Magento integration
An authorised store administrator completes this once. Use four credentials from one dedicated integration. Your store developer can help review version-specific permissions.
Open the integration form
Your Commerce Admin → System → Extensions → Integrations
- Choose Add New Integration and name it Revient (read only). Use your organisation's integration contact email.
- For this manual credential setup, leave Callback URL and Identity Link URL blank. Revient does not provide a Magento token-exchange callback.
- If Commerce requests your current password, enter it only in your own Commerce Admin. Revient never needs that password.
Provider screenshotOfficial Adobe reference: locate Integration Info and API. Use the field instructions above for Revient.Adobe: integration screens and activation ↗ You should seeThe dedicated integration form is open with the API section available.Choose the resources Revient reads
Integration form → API → Resource Access
- Set Resource Access to Custom. Expand Sales, then Operations.
- Select Orders → Actions → View and Shipments. Review automatically selected parent or child boxes before saving; avoid selecting the entire Sales branch.
- Check the permission table against your installed version. If the tree differs, ask your developer to verify the GET orders and shipments route ACLs. Do not solve a missing permission by selecting All.
Provider screenshotOfficial Adobe reference: the resource picker. Follow the permission checklist above, not the selections in Adobe's example.Adobe: integration screens and activation ↗ You should seeThe integration has order-view and shipment access, with unrelated resources left unselected.Activate and collect the four credentials
Integrations list → your Revient integration → Activate
- Save the integration, then activate it. Review the resource list and choose Allow.
- Copy Consumer Key, Consumer Secret, Access Token and Access Token Secret from the resulting token screen into your secure credential manager. All four must come from this integration.
- Finish with Done. Keep the default security settings; do not enable standalone bearer-token use or anonymous API access.
Provider screenshotOfficial Adobe reference: the four field names to copy. Values pictured in documentation are examples, not usable Revient credentials.Adobe: integration screens and activation ↗ You should seeThe integration is Active and you have all four credential values ready for the Revient form.Enter the credentials in Revient
Revient → Integrations → Magento → Connect
- Enter the public HTTPS storefront URL and the four matching credentials. Paste each into the field with the same name.
- Select Connect. Revient signs its API reads with OAuth 1.0a HMAC-SHA256; it does not need your administrator login.
You should seeThe selected store appears in connection management. Any authentication or permission failure is shown before you rely on its evidence.Check one known order and shipment
Revient → selected store → Manage
- Run Check connection, then Sync now. Open the intake queue to follow the job.
- Compare one known order's original ID, currency, total, refund total and date with Commerce Admin. Check a shipped order's tracking reference separately; a successful order probe does not prove shipment access.
- Import payment-provider dispute facts separately when needed. A paid, refunded or shipped order alone does not establish a lost dispute.
You should seeSource order facts are visible in intake. Records without the facts needed for a case stay as drafts.
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 the order customer/email and billing/shipping address fields. Check each shipment separately; a store extension can omit fields without making the connection invalid.
- 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 | Your public HTTPS storefront base URL. Revient adds /rest/V1 itself; do not paste the Admin URL or /rest/V1 endpoint. | https://shop.example.com |
| Consumer keyKeep private | The activated integration's Consumer Key field. | Paste the complete value from your integration |
| Consumer secretKeep private | The same integration's Consumer Secret field. | Paste the complete value from your integration |
| Access tokenKeep private | The same integration's Access Token field. | Paste the complete value from your integration |
| Access token secretKeep private | The same integration's Access Token Secret field. | Paste the complete value from your integration |
If something goes wrong
401 or signature rejected
Check all four values belong to the same active integration. Confirm the server clock and final HTTPS store URL. After reauthorising in Commerce, use Revient Reconnect with the newly issued tokens.
403 / consumer is not authorised
Review the GET endpoint's resource in the installed version's webapi.xml with your developer. Reauthorise after changing API access. Do not grant All or change bearer-token security as a shortcut.
Orders appear but tracking is missing
Confirm the original order actually has a shipment and the integration permits Shipments. The order connection check alone does not validate shipment retrieval.
URL rejected or connection returns HTML
Supply the public HTTPS storefront base, not the Admin login URL. Check REST routing and firewall rules. Redirects and private-network addresses are rejected by Revient.
Common questions
What evidence does Magento supply?
Orders, refund totals recorded on the order, and shipment tracking. Invoices and credit memos are not requested. Payment authorisation is used only when it is already on the order. The lost dispute comes from the payment provider.
Do I need to enable integration tokens as standalone bearer tokens?
No. Revient signs each request using all four OAuth credentials. Leave that provider security setting unchanged.
Is a credit memo proof of a chargeback?
No. A refund or credit memo describes returned money. Import the actual payment-provider dispute record before treating an order as disputed.
What happens when I disconnect?
Revient stops new reads. You can delete the dedicated integration in Commerce Admin to revoke provider access. Evidence already selected for testing remains until you explicitly remove or replace it.
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.
Source documentation
Use these provider pages if a menu name has moved or your plan shows different options.