Authvia Source
Source Info
- The Authvia Source is an Event Cloud source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.
- This source is in Beta
- This integration is partner owned. Please reach out to the partner's support for any issues.
Beta
This feature is in active development and may change before general availability.
TXT2PAY from Authvia is the easiest way to engage your customers for bills, invoices, donations, disbursement and any other payment use cases you may have. Get paid faster without having to worry about PCI compliance.
This source is maintained by Authvia. For any issues with the source, contact the Authvia Support team.
- From your workspace's Sources catalog page, click Add Source.
- Search for "Authvia" in the Sources Catalog, select Authvia, and click Add Source.
- On the next screen, give the Source a name configure any other settings.
- The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The name can be anything, but we recommend using something that reflects the source itself and distinguishes amongst your environments (eg. Authvia_Prod, Authvia_Staging, Authvia_Dev).
- Click Add Source to save your settings.
- Copy the Write key from the Segment UI.
- Go to Connect your Segment account and enter your Authvia Client ID, Secret, and Segment Write Key. You will also pick your region and choose which events you would like to subscribe to. If you do not have an Authvia Client ID and Secret, request access from the Authvia Technical Support team.
Authvia uses the Authvia stream source component to send Segment event data. It uses a server-side Track or Identify method to send data to Segment. These events are then available in any destination that accepts server-side events and available in a schema in your data warehouse that you can query using SQL.
The default behavior is for Authvia to pass the customer reference associated with the payer as the userId.
The table below lists events that Authvia sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations. Authvia includes the userId.
| Event Name | Description |
|---|---|
| Actions Created | An action was created for a customer to complete. An Action could be a payment, signature, data collection and more. |
| Actions Updated | A customer completed the action. An Action could be a payment, signature, data collection and more. |
| Customer Created | A new customer was created in Authvia. |
| Customer Updated | An existing customer was updated. |
| Customer Deleted | An existing Customer was Deleted from Authvia. |
| Business Process Created | A new Business Process (Conversation) was created for a customer. |
| Business Process Updated | A customer has completed some, or all Actions in a business process. Alternatively, the Business Process was cancelled or it expired. |
For a list of properties included in the event payloads, refer to Authvia's Webhook Documentation.