What is Segpay’s Reporting Service (SRS)? In a nutshell, it’s just what the headline above says: a way to make your life easier – assuming, of course, you are a merchant processing payments with Segpay. SRS lets you automate and/or simplify consumer support tasks and the retrieval of key stats about your transactions, all via http requests from your system to Segpay’s.
Why SRS?
One great reason to use SRS is to integrate common support tasks into your existing CRM, so your reps can handle them without having to manually log into the Segpay Merchant Portal every time a customer request comes in. Merchants can also use SRS to reconcile transaction data received in postback notifications.
Consumer Support
Here are a few examples of tasks you can easily integrate into your CRM to save time and simplify consumer support. Please see our documentation for more details about each:
Update a user’s login in the Segpay system
Keep Segpay’s system in sync with yours to ensure we always have the correct usernames and passwords on file to help our support reps provide the best possible service for your members.
Cancel an Account
Cancel a subscription just by entering a specific Purchase ID and a reason. The cancelled consumer retains membership access until the next billing date, at which time the membership expires and a confirming email is sent to the consumer.
Refund a Payment
Refund a specific transaction by sending the transaction ID and a reason. You’ll receive a confirmation that the refund was successful, or the reason it was not (for example, the purchase ID was invalid).
Extend a Membership
Extend a rebill (or expiration) date into the future using this request, by sending the Purchase ID and specifying the number of days to add to the current rebill/expiration date.
Note that this will not alter the consumer’s subsequent billing cycles – meaning, the changed rebill date only applies to the current cycle. The next billing date will be 30 days (or whatever the billing cycle is) from the date the last rebill was supposed to be.
This SRS request comes in handy if you ever have an issue with your website that prevents consumers from accessing their memberships. Use it to simply add the lost time back to their account, instead of having your CS reps login and do it manually.
Reconciling Postback data
Many Segpay merchants are familiar with postback notifications, which “push” important transaction data to them after sales (and other events) are processed by Segpay. Merchants can “pull” the same data via SRS to reconcile what was received in the postback. We recommend pulling the previous day’s transaction data daily, via the following SRS request:
Transactions Purchases by URL
This report gives you a plethora of data – everything you need to manage your consumers and keep track of their subscriptions. It includes the day’s transaction data, including whether each subscription is active, one-time, cancelled or expired. It includes the first 6 and last 4 digits of the cards used, with an indicator for prepaid cards. For void or refund transactions, you will see who processed the transaction, along with the reason and any comments tied to each request.
Note: Make sure you request the latest version of the report (currently that’s version 5).
Once you are approved by Segpay compliance to begin using SRS, you will receive a login that must be included with each request you send (the SRS login is different than your Merchant Portal login). If you have multiple Segpay merchant accounts, you can ask for one SRS login to pull all your accounts in each request. Merchant IDs are included with each record you pull, so you can correctly sort the data on your end.
Have you used SRS to automate or simplify tasks? Are there new SRS reports or tasks you’d like us to add? Please share your thoughts in the comments below or in Segpay’s Ideas Portal.
