The questions people actually ask.

Revient's commerce connectors read evidence; they do not call store endpoints to change orders, issue refunds or take payments. Use the minimum permissions in the provider guide. Some provider permission groups are broader than the read operations Revient uses, and the guide identifies those exceptions.

Relevant orders and genuine dispute records, including available order-time customer/contact and address details, refunds, returns, fulfilments and transaction references. Importing an order alone does not establish a dispute. The connectors do not need full card numbers or a customer-wide export.

Missing, restricted and unsupported source fields remain unknown. For Shopify, protected customer data access is separate from ordinary scopes; adding read_customers alone does not grant access to protected fields.

Revient never contacts your customers. Where you release a case to an approved collection agency, that agency makes contact under the permissions it holds in that market, and only on the cases you released.

New reads stop and connection-bound work checks the current connection before writing. Existing cases and their source history remain in your workspace. Evidence-testing records are retained until an authorised removal or replacement instruction; production retention periods remain unresolved in the draft legal documents.

Your workspace, and Revient staff acting on a support or operations task. Staff actions are recorded as staff, from the internal system, and are never made to look like something you did.

A partner organisation sees only the cases matched or released to it, and reading sensitive raw content is itself recorded. There is no pool of merchant data for a partner to browse.

No. Revient holds no third-party security certification and has not had an independent penetration test. Store and provider credentials are encrypted where they are stored, and the key is currently held by the application rather than by a managed key service.

This is on the trust page rather than hidden because a security answer that overstates itself is worse than a gap.

Revient collects the records for each lost chargeback and runs its evidence checks. Only chargebacks you lost are scored, and Revient AI reads a case only where you have allowed it. Progress shows each stage and any failure. Ordinary orders are not treated as disputes.

A Shopify sync imports every confirmed lost chargeback, whatever the order's age. Carriers such as UPS delete tracking history after about 120 days, so Revient also uses the proof you submitted to Shopify when you disputed the chargeback. It reads that evidence from Shopify where Shopify grants access; otherwise upload the same files to the case under Add evidence. Revient reads a proof of delivery PDF or screenshot and counts the delivery when it names the order's tracking number. Existing cases keep refreshing.

A lost chargeback missing some details appears as Needs information. Open, won and pending disputes are skipped. Revient never guesses a missing fact.

It explains selected evidence and answers from your authorised case summary and Revient help. It cannot contact customers, release cases, sell receivables or make payments. The evidence checks and existing evidence keep working if Revient AI is unavailable.

Mailbox messages need a separate permission before Revient AI reads them. Revient encrypts what it stores from each AI answer and asks its AI provider not to keep the request, though that request alone does not guarantee the provider keeps nothing.

The current workflow keeps real corrections and review material within your workspace. Shared improvements use reviewed synthetic examples, and Gmail-derived material is excluded. Calling a model API does not retrain it. Changes need evaluation and approval before release.

Automatic tracking registration is limited to confirmed lost dispute cases and requires the operator to verify that tracking notifications are disabled. Revient omits customer contact fields. Carrier delivery, a signature and a photograph are separate evidence facts; an empty proof field is not proof of delivery.

Professional organisations. Applications are reviewed by hand at organisation level, and approval is granted for specific capabilities in specific jurisdictions. Being approved to work one market does not approve you for another, and it does not approve you to buy.

No. A receivable is only ever sold to an approved organisation holding an active debt-purchase approval for that jurisdiction. A person can use buyer functionality only as an authenticated representative of that organisation. Revient is not a retail marketplace and does not sell debt to private individuals.

You apply as an organisation and name debt purchase as one of the capabilities you are asking for. Applying records a request, and a request grants nothing.

Approval follows a documentation and jurisdiction review, and it is granted market by market. Being approved to collect in a market never grants approval to buy in it, and neither approval carries into a market that has not been reviewed.

Only the opportunities offered to that organisation, and only what the stage of the work justifies. Before an assignment exists the view is purpose-limited and carries as little personal data as the task allows.