Category Archives: Industry Terminology & Miscellaneous Topics

GPT / PTS / CPA Industry Terminology & Miscellaneous Topics

Early ‘Legacy’ Documentation (Very Basic & Mostly Outdated)

Domain

Purchase a domain if you haven’t yet and update the name servers to point to NS1.SHIFTCODE.COM and NS2.SHIFTCODE.COM.

You must have ownership and control over a domain name in order to fully setup your site. Domain names can be purchased for various prices from companies such as http://godaddy.com, http://namecheap.com, or others. After you have purchased, or if you already own a domain name, please read below to finish configuration.

 

Domain Name Setup

 

To get your domain name working properly, you will first need to login to manage your domain name. Wherever you purchased the domain name from is where you would login at to manage it. Once logged into your domain registrar, navigate to the name server section and update them to the following:

 

NS1.SHIFTCODE.COM
NS2.SHIFTCODE.COM

 

Name server updates could take up to 12-48 hours to fully update across the Internet so have patience during this time.

 

Changing Domain Name

 

Domain name changes are only permitted if you are the original owner of the website or if you have owned the website for at least 90 days. If you need to change your domain name to a different name, you must first purchase the domain and update the name servers (to the name servers listed above). Once you have finished purchasing and updating name servers, please submit a ticket requesting a domain change. Please note that there is a charge involved in having this done.

 

Renewing Domain Name

 

Please note that we have nothing to do with renewing your domain name. All domain names must be renewed through the domain registrar in which you purchased the domain name from.

 

 


 

Admin Panel

Access your administration panel through the link that was emailed to you or by logging in through http://shiftcode.com website itself.

Configure

Find the Configure link within your admin panel and set the E-mail address you want users to see when they register. Also setup the payment methods you accept if you allow ads, upgrades, or items to be purchased.

Product Configuration – Contact Form

Under Products, find the Contact Form link. Enter the e-mail address where you wish to receive the messages sent through the contact form.

Product Configuration – Membership

Under Products, find Membership → Configure → Security. Set how you want the system to react against members when they login and choose which countries you want to allow registration to. Several other options can be found on the main Configure page as well as the Registration page. Browse through and read through the help icons to setup optional items as desired.

Product Configuration – Withdraw

Under Products, find the Withdraw link. Choose a method from the dropdown list (such as PayPal) and click Add Method. Configure the setup as desired and click Add Method.

Downtime

Click Configure → Downtime. You can put your site in construction mode so visitors cannot see your website. There is an option to put in IP addresses allowed to visit your site as well. The downtime option is often used when just starting up your website or when you are going under major changes and don’t want others to have a sneak peek.

E-mail

Click Configure → E-mail. When users register to your website or when they receive any e-mail from you that you send out, they will see the “From Name” and the “From E-mail” that you have setup. So simply provide the name and the e-mail and save your changes. In E-mail → Alerts, you can choose which e-mails you’d like to receive. In Configure → Messages, you can customize e-mails that your members receive.

IP List

Click Configure → IP List. Block certain countries, IP addresses, and/or ISP providers from accessing your site.

Payment Methods

Click Configure → Payment Methods. Setup payment methods you are willing to accept when members purchase items from your site.

The ShiftCode GPT Script Offer Sorting Issue and Workaround Advice

This is a known issue with the ShiftCode GPT script. ShiftCode coders are aware of the issue and they are working on a permanent fix.

The Script Behavior Symptom:

When a member uses the ‘Sort By’ while viewing a list of offers then as soon as he/she clicks the ‘Submit’, Ignore’, or ‘Report’ button then the offers list reverts back to the default search (rather than continuing the ‘Sort By’ offer sort previously chosen by the member)

An Inconvenient But Effective Workaround:

Tell your members that as soon as he/she clicks a ‘Submit’, Ignore’, or ‘Report’ button then wait for the page to load fully and then hit their browser’s ‘Back’ button to return to the previously selected search order (where they left off)  In fact you may want to post a reminder message as text just above each offer display.

Site Design, Script, & Coding Terminology

  • CSV– The abbreviated term CSV stands for ‘Comma Separated Values’ and is usually used to describe the format of a text file database of information.  In a CSV file the data values are individually divided by inserting a comma (“,”) in between each value. CSV data files can be viewed in any text editor such as Notepad (notepad.exe) which comes standard with any Microsoft Windows operating system but CSV files are best displayed while loaded into a spreadsheet application such as Microsoft Excel (part of Microsoft Office)  Microsoft Excel can load a CSV files directly.

This Knowledgebase Article To Be Continued (a work in progress)

Historical Information Previously the ShiftCode Wiki Site (Archived)

So as the information on the former (years ago) original ShiftCode Wiki documentation site is not entirely lost to time we have located a partially complete generally hard to work with (though helpful if you are persistent and have patience) remaining archival copy of the site on the Internet Archive ‘Wayback Machine’ here: https://web.archive.org/web/20130209035325/http://shiftcode.com/wiki/API

This archive contains crucial information regarding the ShiftCode API including a class download with an example game, full API documentation, and other useful tidbits of information on various other topics.

The original ShiftCode.com site has an archival view starting here:  https://web.archive.org/web/20060324182331/http://shiftcode.com/

The original PerformaNetwork.com site has an archival view starting here:  https://web.archive.org/web/20120112055553/http://www.performanetwork.com/

This Knowledgebase Article To Be Continued (a work in progress)

GPT & CPA / Affiliate Network Industry Terms

  • GPT– The term GPT stands for ‘Get Paid To’ which in our context describes a type of site in which site members are rewarded with cash (delivered through an online payment processor such as PayPal, etc.), loaded on to a prepaid debit card (delivered via postal mail or the card specifics emailed), or via mailed money order or check, etc.) or prize rewards such as mailed physical prize (can be anything at all), services, site account upgrades, online game currency, or purchased (traded for points) online advertising, etc)
     
  • PTS– This term stands for ‘Paid To Signup’ and generally is used interchangeably with the term ‘GPT’ (though nowadays the term ‘PTS’ is in decline in favor of the more popular ‘GPT’)  PTS is also sometimes used more specifically to describe a type of ‘offer’ in which the advertiser pays only for registrations or ‘sign ups’
     
  • Affiliate Network– [Ad Network / CPA Network] A company which solicits, negotiates, and contracts with advertisers (in some (many) cases – other affiliate networks) maintains an inventory of ad campaigns and offers (sourced from advertisers) while also maintaining a stable of publishers / affiliates which have applied and have been pre-screened by the network to promote their listed ad campaigns.
     
    The advertiser purchases promotion services for their ad campaigns and offers from the affiliate network which in turn generally sets the lead rates (commonly calculated as a percentage portion of the advertiser lead rate the network receives), organizes and presents crucial offer promotion terms information (types of allowed promotion forms and offer restrictions, etc.), oversees publisher compliance with the offer terms, enforces offer fraud prevention, serves banner creatives and tracking links, facilitates (approves or denies) publisher access to each specific campaign, pays publishers based upon their individual performance, and utilizes a leased (usually) affiliate network tracking and management web site script.  In our (ShiftCode) case our own in-house proprietary Performa Network script is ideally integrated with our GPT site script product resulting in many advantages over all other (disjointed) commercial network scripts.                       
     
  • Advertiser– A company or individual with a goal of promoting a brand, product, or service by way of an advertising campaign and/or offer seeking to compel or entice the consumer (GPT site member / offer respondent / end user – in our context) to make a purchase, perform a certain action(s), be educated by the information provided (favoring their ‘brand’)  The advertiser is responsible for compensating the CPA / affiliate network for offer completions (leads and/or conversions) based upon the terms of the contractual obligations predefined or negotiated beforehand.
     
  • Publisher– In our context in this industry (online electronic) and in this day and age the term ‘publisher’ refers to a company or individual who has the role of promoting advertising campaigns and offers listed in the advertisement (ad) ‘inventory’ of the affiliate network and/or directly from the ‘advertiser’   The publisher has the responsibility of delivering publicly (or ‘publishing’) the advertisement(s) to the offer respondent most commonly by way of a web site (a prime example in our context would be a GPT web site though this may also take other forms such as a social network (Facebook, etc.), niche web site (or blog), etc.) banner ad and/or link , via email to a database list of newsletter subscribers the publisher maintains, and by other electronic means (though less common it doesn’t necessarily have to be electronic – some publishers may promote ad campaigns by way of printed hardcopy (physical) ‘flyers’, by postal mail, etc)
     
    The term publisher is often used interchangeably with the term ‘affiliate’ in the context of an ‘affiliate network’ though sometimes the use of the term affiliate may indicate a dual role as both advertiser and publisher in relation to an affiliate network.     
     
  • CPA– The term CPA stands for ‘Cost Per Action’ and describes a mode of offer delivery where the ‘advertiser’ pays only for a predefined and agreed upon specific ‘action’ performed or landmark point reached towards offer completion (what’s called an offer ‘conversion’ or a ‘lead’ generated)
     
  • Offer– An advertiser’s presentation of a product or service to the GPT site member (offer ‘respondent’) in the form of a web site or page linked to from a ‘banner’ (logo image, etc) and/or text link.  Am offer relays details of a specific deal(s) intended to entice the offer respondent towards completing a specific action(s) such as a purchase or a sales lead.   The terms ‘offer’ and ‘campaign’ are often used interchangeably (incorrectly in my opinion)  though technically an advertising campaign may contain one or more offers.
     
  • Campaign– An advertiser’s presentation in the form of one or more ‘offers’ toward the same or similar goal describing a specific brand, product, or service to the GPT site member (offer ‘respondent’)  An advertising campaign is a single offer or group of offers relating to the same or similar ‘deal’ presented to the respondent.
     
  • Incent vs. Non-Incent– (offer promotion types) Generally, you (we) ARE in the GPT site business and most all (if not 100%) of the offer promotion we will actually be doing (or ‘seen always’ by advertisers as doing) falls into the ‘Incentive’ (‘incent’ for short) category.  Incent promotion means that you will be offering an incentive to your GPT site members for them to engage in the act of what we (in the business) call ‘doing offers’  Incentives (sometime called ‘rewards’) come in all types (cash, points, virtual currency, prizes, site account upgrades, access to restricted content, etc.) and if you are providing ANYTHING AT ALL to anyone in return for them attempting and completing offers then you are indeed engaging in incentive based promotion methods (it’s best NOT to ever try to hid that simple fact – us being in this business)  Anyways, it is rather simple for advertisers and affiliate networks to distinguish what is incent type promotion traffic patterns versus non-incent patterns simply by glancing at the detailed traffic reports available to even the simplest of affiliate network administrator.

    Ok, we’ve covered incent type promotion but what about non-incent promotion?  Sure, non-incent offer promotion can basically be summed up simply by this test.  Is the offer respondent clicking upon the offer banner / link completely out of his own curiosity or desire to learn and know more about the brand, product, or service?  …or is the offer respondent click based upon anything (at all) that has been promised, implied, or reasonably expected based upon the type of site (GPT?) he is seeing the offer promoted on?  Even allowing access to privileged access ‘premium’ web site content IS considered INCENT promotion (it’s called a ‘content locker’)

    This looks like a perfect place to briefly mention that ‘tricking’ anyone to click on an offer link or fooling anyone into completing an offer is considered ‘FRAUD’ – the LEAST of your worries would be that your offer source will call you out for it being ‘incent’ traffic (they’ll be much more likely to suspend (or revoke) your publisher account without payment if they discover the deceptive practice you’re perpetrating upon their valued potential customers – while also implicating them (or their brand) in cheating the public in any way)  It’s dishonest FRAUD to trick, fool, or force anyone to complete offers you are promoting.  Just DON’T!
     
    With most all modern savvy advertisers and affiliate networks then there is no wiggle room or grey area here.  It is either clearly non-incent promotion (and if not, then it IS INDEED implied that it’s incent.)  It’s not something that is easily successfully argued about with the people who are paying for you to promote their ads.  If you become too argumentative or bold in your assertions that ANY of the traffic you are sending them after declaring that you are in the GPT site business is not incent type traffic then they will be more likely than not to reverse your credit for any questionably promoted offers previously approved – after the fact (and payment for those leads – called a ‘reversal’ or ‘charge-back’) than they would to pay you for risky (possibly fraudulent – on YOUR part) leads.

    Remember, in most all cases the people (advertiser or ad network) you are talking to also have people ‘upstream’ (traffic wise) that they will ultimately have to answer to about questionable leads (just as you are – with them)  …and they would rather not risk that they themselves will ultimately not get paid from their offer source (as much as (if not more) than YOU want to always be sure that you are getting paid for completions that you are paying (usually far in-advance) your own GPT site members for)  To sum it all up – don’t put yourself in the position of having to defend what are classic risky (looking) leads.  If you do legitimately have other web sites that are indeed non-incent sources of traffic then discuss the issue with your offer sources beforehand and if they give you an allowance that they trust you that you also legitimately have non-incent traffic as well (at other sites) then do yourself a favor by keeping incent traffic and non-incent traffic completely separate business by having separate publisher accounts for each traffic type (if allowed) with your offer sources.
     

  • Reversals / Charge-Backs / Holds– Your credit toward payment for offer ‘leads’ (credited offers – sometimes also called a ‘sale’ or ‘conversion’) is never set-in-stone!  The news will likely come in the form of an email from some obscure sounding ‘compliance department’ or ‘best practices’ part of your upstream offer source (ad network or advertiser)  Your first reversals (or batch of them) will not likely be your last.
     
    Everyone gets reversals once in a while for one reason or another it’s best not to succumb to your initial reaction to fly off the handle and get loud or emotional over it – and definitely don’t make rash decisions you may regret later on when you know more about the situation (don’t take an attitude or get loud when investigating further with your offer source – reversals are best dealt with by calmly investigating all the information your have on hand (usernames, IP addresses, etc) in an attempt to locate the culprit.  It’s not uncommon (unfortunately) for any of your upstream offer sources to reverse credit (payment) on any one lead (or sometimes even in bulk mass reversals) based upon a large number of factors a few (of many) of which reasons might be:
     
    — Fraud / Bogus Fake Information –Pay attention to these reports and if the same names of your GPT site members show up repeatedly over time then perhaps it’s time you send that / those members a polite but firm reminder to your specifically named site member(s) that them giving your valued advertising sponsors fake / false information is not at all acceptable.  Put them on notice that they have been noticed and if it happens again then go with your gut as far as suspending such a member.
     
    — Temporary / Disposable Email Addresses –  Yes, when you are selecting and writing your site’s Terms of Service (TOS) which are basically the rules (aimed at members) of your GPT site then you would want to mention that the use of fake / temporary / disposable email addresses are never ok to use while completing offers on your site.  Basically, the advertisers are paying for legitimate reliable contact information that they can use to build a database of real and truly interested persons with regards to their brand, product, or services (especially with ‘email submit’ type offers)  If a member is using a temporary disposable email address then that member is in-effect cheating the advertiser of their future opportunity to contact someone who has appeared to express an interest in seeking more information from the advertiser.  If the email address bounces a day later when the advertiser attempts contact then that will leave a bad-taste-in-their-mouth (so to speak) for the advertiser with regards to the quality of your site’s traffic quality – it will eventually reflect DIRECTLY on your own bottom line (members of your site – and the responses they give in responding to offers – represent your site’s overall traffic quality and the advertiser’s return-on-investment of their advertising dollar)
     

    Pixel Manipulation– Faked ‘firing’ of the ‘pixel’.  A tracking pixel is one of a multi-layered mechanism for tracking and crediting offer completions (a universal method adopted universally by the industry)  This fake pixel firing issue has been happening in the industry with increasing frequency and depth of depravity as years go by.  It’s an industry wide phenomenon though we can report that our (ShiftCode) security updates have nearly eliminated the issue on our systems.  Since this is a public web site and the subject is sensitive to the industry then we’ll choose not to go into any more detail here only to say that if you get curious then simply Google the subject (or if you are having an issue specific to your GPT site or network then feel free to contact ShiftCode support for help.

This Knowledgebase Article To Be Continued (a work in progress)

Functions & Template Variables


NOTE: This is Historical Information About the Now Inoperative ShiftCode API – Reproduced Just for Saving the Info for the Future

The API product allows you to easily build your own custom applications on your own server.

You can download the latest PHP classes here:  api-1.1.0.zip
The file includes a demonstration game of Heads or Tails!

Functions

Name Function Multiple Support
Jackpot – Add Entries JackpotAdd no
Paid to Signup – Load Ad PtsLoad no
Shoutbox – Post ShoutboxPost no
User – Balances UserBalances no
User – Load UserLoad no
User – Login UserLogin no
User – Register UserRegister no
User – Cash Transaction UserTransCash YES
User – Points Transaction UserTransPoints YES

Additional Options

Template Variables

If you wish to include stats from your own server, you can include them in your template by creating an XML file on your server formatted like the one below.

<?xml version="1.0"?>
<template>
	<stat1>234</stat1>
	<stat2>865.23</stat2>
</template>

You can pass a user’s id to your XML file like so:
http://example.com/template.php?uid={~$user.id~}

The stats can be displayed in your template by using the following code:

Stat 1: {~$api->template('stat1')~}
Stat 2: {~$api->template('stat2')~}


API:Multiple Support

If a template function has multiple supports it means more than one request can be sent to it.

Usage

Take for example we wanted to credit the user $0.20 and $0.40 as separate transactions.

Example Code

$sc->userTransCash(array(
	array(
		'trans_user' => 1,
		'trans_amt' => .20,
		'trans_type' => 'credit',
		'trans_name' => 'Winner',
	),
	array(
		'trans_user' => 1,
		'trans_amt' => .40,
		'trans_type' => 'credit',
		'trans_name' => 'Winner',
	),
));
 

API:JackpotAdd

From ShiftCode
 
Request Variables
Variable Example Value Required Description
jackpot_id 1 Yes The jackpot the entries are being added to. (1-5)
jackpot_amt 1.00 Yes The amount being added to the jackpot.
jackpot_entries 2 Yes The number of entries being given to the user.
jackpot_uid 1 Yes The unique identifier of the user getting the entries.

Response Variables

Variable Example Value Description
success 1 The entries were successful added.

Example Code

$sc->jackpotAdd(array(
	'jackpot_id' => 1,
	'jackpot_amt' => 1.2,
	'jackpot_entries' => 2,
	'jackpot_uid' => 1,
));

API:PtsLoad

Request Variables
Variable Example Value Required Description
pts_id 1 Yes The unique identifier of the offer being loaded

Response Variables

Variable Example Value Description
pts_id 1 The offer’s unique identifier
pts_name Great Deals The name of the offer.
pts_siteURL http://shiftcode.com The URL of the offer.
pts_bannerURL http://shiftcode.com/images/banner.gif The URL of the banner for the offer.
pts_code   HTML Code to display the banner and site URL.
pts_requirements   The requirements of the offer.
pts_cash 1.00 The cash amount given to a member for the offer.
pts_cid 1 The category the offer is in
pts_cashAdv 2.00 The cash amount the advertiser pays for the offer.
pts_cashback 10 The percent of a sale given to a member for completing the offer.
pts_points 1 The points amount given to a member for the offer. (→ Points System product required)
pts_jackpot   If the field is not blank then the user gets jackpot entries. (→ Paid to Signup Jackpot product required)
pts_min 0 Minimum number of offers a member must have completed before attempting this offer.
pts_redoWait 0 Number of days before a user can attempt this offer again.
pts_redoFolder 0 The redo wait is factored based on the pending (0) folder and the completed (1) folder.
success 1 The offer was successful loaded.

Example Code

$response = $sc->ptsLoad(array(
	'pts_id' => 1,
));
echo $response->pts_name;

API:ShoutboxPost

Request Variables
Variable Example Value Required Description
shout_name John Yes The name of the user posting.
shout_msg Hi everyone Yes The message being posted.
shout_uid 0 No The user ID of the user posting. (→ Membership product required)
shout_ip 1.1.1.1 No The IP address of the user posting.

Response Variables

Variable Example Value Description
success 1 The message successful posted

Example Code

$sc->shoutboxPost(array(
	'shout_name' => 'Admin',
	'shout_msg' => 'Hello everyone, I am using the API.',
	'shout_uid' => 1,
));

API:UserBalances

Request Variables
Variable Example Value Required Description
user_ids 1,2 Yes The unique identifier of the user(s)

Response Variables

Variable Example Value Description
balances
{
  "1" : {
    "id": 1,
    "balance": 0.5,
    "points": 0.5
  },
  "2" : {
    "id": 2,
    "balance": 0.5,
    "points": 0.5
  }
}
An object which contains each user and their balances.
success 1 The user was successful loaded.

Example Code

$response = $sc->userBalances(array(
	'user_ids' => '1,2,3',
));

// User with the ID of 1
echo $response->balances->{'1'}->balance;
echo $response->balances->{'1'}->points;

// User with the ID of 2
echo $response->balances->{'2'}->balance;
echo $response->balances->{'2'}->points;

API:UserLoad

Request Variables
Variable Example Value Required Description
user_id 1 Yes The unique identifier of the user being loaded

Response Variables

Variable Example Value Description
user_id 1 The user’s unique identifier
user_first John The user’s first name
user_last Smith The user’s last name
user_username johnsmith The user’s username
user_email johnsmith@gmail.com The user’s e-mail address
user_cash 1.00 The user’s current cash balance.
user_cashTotal 1.00 The user’s lifetime cash balance.
user_points 1.00 The user’s current points balance. (→ Points System product required)
user_pointsTotal 1.00 The user’s lifetime points balance. (→ Points System product required)
user_dateRegistered 2010-07-11 11:52:32 The date of when the user registered.
user_dateActive 2011-01-05 13:02:33 The date of when the user was last active.
user_ip 1.1.1.1 The user’s current IP address.
user_geoCountry United States The user’s country based on their IP address.
user_geoRegion New York The user’s state, province or region based on their IP address.
user_geoISP RCN Corporation The user’s Internet Service Provider based on their IP address.
user_page /members/index.php The last page the user was seen on.
user_upgradeID 1 The unique identifier of the upgrade this user is assigned to. (→ Upgrade product required)
user_upgradeName Basic The name of the upgrade this user is assigned to. (→ Upgrade product required)
user_status Member The user’s current status.
user_verified 0 The user’s verification level.
success 1 The user was successful loaded.

Example Code

$response = $sc->userLoad(array(
	'user_id' => 1,
));
echo $response->user_username;

API:UserLogin

Request Variables
Variable Example Value Required Description
cookie username|passwordhash Yes A dump of the user’s cookies containing their login token, the name of the cookie is SC_member
server_ip 1.1.1.1 Yes The user’s IP address
server_agent Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 Yes The user’s browser agent
server_language en-us No The user’s browser language
page /headsortails/index.php No The page the user is currently on

Response Variables

Variable Example Value Description
user_id 1 The user’s unique identifier
user_first John The user’s first name
user_last Smith The user’s last name
user_username johnsmith The user’s username
user_email johnsmith@gmail.com The user’s e-mail address
user_cash 1.00 The user’s current cash balance.
user_cashTotal 1.00 The user’s lifetime cash balance.
user_points 1.00 The user’s current points balance. (→ Points System product required)
user_pointsTotal 1.00 The user’s lifetime points balance. (→ Points System product required)
user_dateRegistered 2010-07-11 11:52:32 The date of when the user registered.
user_dateActive 2011-01-05 13:02:33 The date of when the user was last active.
user_ip 1.1.1.1 The user’s current IP address.
user_geoCountry United States The user’s country based on their IP address.
user_geoRegion New York The user’s state, province or region based on their IP address.
user_geoISP RCN Corporation The user’s Internet Service Provider based on their IP address.
user_page /members/index.php The last page the user was seen on.
user_upgradeID 1 The unique identifier of the upgrade this user is assigned to. (→ Upgrade product required)
user_upgradeName Basic The name of the upgrade this user is assigned to. (→ Upgrade product required)
user_status Member The user’s current status.
user_verified 0 The user’s verification level.
user_loggedIn 1 If the user is logged in (1) or not logged in (0).
success 1 The registration was successful

Example Code

$user = $sc->isLoggedIn();

API:UserRegister

Request Variables
Variable Example Value Required Description
user_first John Yes The user’s first name
user_last Smith Yes The user’s last name
user_username johnsmith Yes The user’s username
user_password johnsmith123 Yes The user’s password
user_email johnsmith@gmail.com Yes The user’s e-mail address
user_ip 1.1.1.1 Yes The user’s IP address
user_referrer 0 No The referrer’s ID number
user_refURL http://google.com No The URL from where this user came from.
user_balance 0.00 No The balance to start the member off with.

Response Variables

Variable Example Value Description
success 1 The registration was successful

Example Code

$sc->userRegister(array(
	'user_first' => 'John',
	'user_last' => 'Smith',
	'user_username' => 'johnsmith',
	'user_password' => 'johnsmith123',
	'user_email' => 'johnsmith@gmail.com',
	'user_ip' => '1.1.1.1',
));

API:UserTransCash

Request Variables
Variable Example Value Required Description
trans_username johnsmith Yes The username of whom the transaction is for.
trans_type credit Yes Can be either credit or debit.
trans_amt 0.01 Yes The amount of the transaction.
trans_name Adjustment Yes The name of the transaction that will appear in the user’s history.

Response Variables

Variable Example Value Description
success 1 The transaction was successful

Example Code

$response = $sc->userTransCash(array(
	'trans_user' => 1,
	'trans_type' => 'debit',
	'trans_amt' => 0.01,
	'trans_name' => 'Adjustment',
));
if(isset($response->success))
{
	echo 'Successful Transaction';
}

This function has Multiple Support.


API:UserTransPoints

Request Variables
Variable Example Value Required Description
trans_username johnsmith Yes The username of whom the transaction is for.
trans_type credit Yes Can be either credit or debit.
trans_amt 0.01 Yes The amount of the transaction.
trans_name Adjustment Yes The name of the transaction that will appear in the user’s history.
trans_preventnegative 0 No If set to 1 and the type is a debit then this will prevent the transaction if it concludes with the user having a negative balance.

Response Variables

Variable Example Value Description
success 1 The transaction was successful

Example Code

$response = $sc->userTransPoints(array(
	'trans_user' => 1,
	'trans_type' => 'debit',
	'trans_amt' => 0.01,
	'trans_name' => 'Adjustment',
));
if(isset($response->success))
{
	echo 'Successful Transaction';
}

This function has Multiple Support.


You can view and copy the source of this page: