Operations and Administration

Reporting

Strivve provides both API card placement result notifications and out of the box reporting solutions to support your card placement reporting needs.

CardSavr Webhook Notifications

For the best integrated reporting solution, Strivve recommends leveraging Webhooks available via the CardSavr API. Webhooks provide your application the ability to receive asynchronous events for all card placement results. By registering for these events, your integration can streamline real-time results into your targeted data ingestion processes for back office applications.

When creating a cardholder, integrators can also include their own custom_data that can tie additional application-specific cardholder details back to the back office processing when receiving notifications for a given cardholder placement transaction. This provides a tight integration from which a cardholder along with any specific attributes can be specified and fully tracked upon receiving these notifications.

Strivve Partner Portal

Each dedicated CardSavr instance includes a Partner Portal used in the administration of your environment configuration. Belsow are the out of the box reporting options that your organization may generate at any time.

Merchant Reports

Merchant Reports allow you to generate a report of all card placement activity between any specified dates.

To generate the report, simply select the start and end dates and generate the report. The report will then be downloaded to your device. Reporting Reporting

Field NameDescription
Field NameJob id of the transaction
bank_identification_numberBank id of the card associated with the placement transaction
merchant_site_hostnameHostname of the merchant site the card is being place to
statusResulting status of the card placement transaction
fi_nameName of the associated financial instituion (configured in the Partner Portal)
fi_lookup_keyKey used to identify financial institution used by API (configured in the Partner Portal)
completed_onTimestamp of when card placement transaction completed
meta_key (not pictured)Comprised of the first and last initials of the cardholder, the postal code, and the last two digits of the PAN.
cuid (not pictured)Unique ID for the cardholder provided by your application to the CardSavr API. A random number will be generated if not provided.
custom_data (not pictured)Additional data that can be added to the cardholder by your application to the CardSavr API. If provided, the merchant report will include this information in additional fields.

Cardholder Session Reports

Strivve is in process of developing a cardholder session report that details CardUpdatr or StrivveCX UX data that can track the full Strivve UX session journey while linking to the placement transaction detail provided in the merchant reports.

This section will be updated once the session reporting feature is available.

Merchant Site Reports

The Merchant Sites report lists all Strivve supported merchant sites and their current status, as well as other relevant information. Reporting

*Strivve is currently working on additions to this list that includes additional information per site plus the ability to export to your device.

Previous
Partner Portal