Customer Registration

Versa routes receipts by matching against registered customers. Every time a sender (e.g. an airline, an E-commerce merchant) makes a sale, they check to see if one or more clients (e.g. an expense management app) are authorized to pull down receipts for that customer. For example: if Supplier A completes a sale to 'jshmoe@acme.com', and if Expense Management App B has registered as an authorized receiver of 'acme.com' receipts, then Versa will direct Supplier A to forward the encrypted receipt to Expense Management App B.

How It Works

Customers must explicitly grant clients permission to share receipts on their behalf.

Registering and de-registering is typically performed via Versa Link. The Versa developer portal also provides a user interface to perform this action, which can be especially useful for whitelisting customers in early phases of implementation.

API Access

Not seeing what you're looking for? We grant programmatic access to customer registration APIs on an as-needed basis. Contact us at support@versa.org if you'd like to learn more about this feature.

Receiver vs. Sender Customer Registration

Both receivers and senders can register customers, however these two types of registration have different scopes.

Receivers register customers to receive receipts from any sender. For example, when an expense management app gets permission from a customer to collect receipts on their behalf, they will receive receipts from all participating sender merchants.

Senders, on the other hand, can only register customers to receive the receipts from their direct sales. E.g. a travel manager admin who is logged in to the company settings screen on the 'Nimbus Airlines' website could opt to push their Nimbus Airlines receipts to their expense management app, but they would not be able to turn on universal receipt sync from within the Nimbus Airlines website.

Sender and receiver registrations are not mutually exclusive. For instance: if Sender A registers a customer for Receiver B, and Receiver B also registers that same customer, Versa will match against both registrations, and return a single reference to Receiver B.

Sender Registration, "Merchant Group Codes", and "Merchant User Codes"

In addition to the standard domain and email -based forms of customer registration, senders can also register customers using a "merchant group code" (MGC) or a "merchant user code" (MUC).

A merchant group code is a unique identifer assigned to a corporate program. For example, a rental car company might have a 'corporate discount code' for Acme Co.

A merchant user code is a unique identifer assigned to an individual user. For example, an airline might have a loyalty program id for each of their frequent flyers.

'MGC' and 'MUC' handles give merchants the flexibility to register customers according to these core identifiers in their system, alongside more universal identifiers like domain and email.

Note: usage of 'MGC' and 'MUC' customer registration is currently invite-only. Contact Versa Support if you’d like to learn more about this feature.

Listing & Querying Receivers

If you are using sender registration, you can query our network of registered receivers using the Receiver Query API.