Feb
14

Five Reasons Why Salesforce.com’s Chatter Will Fail

I have been watching the concept of Chatter for a while now. On the one hand, I could kick myself for not making more hype out of Sugar Feeds, the exact same functionality Sugar has had in its product for more than a year prior to availability of Chatter. My bad.

On the other hand, I think Chatter has been over-hyped in a dangerous way, one that will lead to failure for Chatter as a product line for Salesforce.com.

And since I’m feeling particularly snarky on this pre-Labor Day Friday, I thought I’d jot down a “top 5″ list of reasons why I think Chatter will prove yet another one of Salesforce.com’s interesting, but ultimately unprofitable ventures.

Here we go…

1. Chatter is only an internal collaboration tool. There are many of these available, but more important is the fact that if Chatter is the lynch pin of Salesforce.com’s “social” strategy it is missing one very important thing Read the rest of this entry »

Feb
14

Why Salesforce.com’s Social Media Smarts Could Get You Closer to Customers

When it comes to social media, Salesforce.com leads rivals like Oracle and SAP — and its success could help your company reach customers. Case in point: Salesforce.com apps now work with social networking services like Twitter and Facebook.
By C.G. Lynch
Thu, March 26, 2009
Add a comment

CIO — At a time when many companies still struggle to manage the rise of social networks and understand what the trend means to their organizations, Salesforce.com has begun tailoring its business software to help people harness the power of social media. During the past year, the company has taken several steps to make its core products work alongside popular consumer applications like Facebook, Google and Twitter. Read the rest of this entry »

Jun
20

New Payment Form Customization Options

These enhancements will allow you to better integrate the payment form and receipt page to the look and feel of your merchants’ websites.

You can now customize the section heading text as well as the body text, including font type, style, size and color. You can select from a range of colors provided, or enter a color code to display a specific color.

To customize the payment form and receipt page using the new options:

  1. Log into the Merchant Interface at https://account.authorize.net
  2. Click Account from the main toolbar
  3. Click Payment Form under Transaction Format Settings
  4. Click Color and Font Settings
  5. Make any necessary changes
  6. Click Preview to see how your changes will look or click Submit to save your changes
  7. If at any time you would like to revert to the default payment gateway settings, select Reset Defaults.

We hope these changes will help create a more seamless transaction experience for your merchants’ customers.

 

Jun
20

Introducing getUnsettledTransactionList and getBatchStatistics

Two new calls to the Transaction Details API, getUnsettledTransactionList and getBatchStatistics.

getUnsettledTransactionList returns up to 1,000 unsettled transactions per call, returning the most recent transactions. The information returned in the response will be the same as what’s returned in getTransactionList call.

getBatchStatistics returns the batch stats for a single batch like settlement state and time, charge count, decline count, etc.

For more info, check out the XML guide and the SOAP guide.

Retrieving transaction details through the Transaction Details API is Authorize.Net’s solution for developers looking to extract reporting and statistical data on existing transactions.

Gaining access to the details of previously processed transactions is important for reporting and reconciliation. The Transacton Details API allows merchants to retrieve the following sets of data:

  • Batch settlement information, including statistics broken out by payment type.
  • Limited transaction details for specific batch requests.
  • Full transactional details for specific transaction IDs.
  • Limited transaction details for unsettled transactions.
  • Batch statistics by payment type for a specified batch ID.

 

Jun
20

New Hosted Option for CIM

The hosted CIM option provides a way for you to establish a hosted connection with Authorize.Net that allows the exchange of sensitive cardholder data to happen on our secure servers instead of the merchants’ servers.

 

The hosted CIM is available to all developers now, however, the feature is not yet being publicly announced as it’s still officially in beta. For more information on the hosted CIM option, please see section two of the CIM XML Guide and the CIM SOAP Guide.
A hosted CIM solution was one of most-requested features from many of you, and we hope this release will help alleviate some of the scope and complexity of PCI DSS compliance.

May
06

Reminder to Download Transactions

Our latest Developer Center release is now complete. Any of the bugs or errors reported to us concerning the SDKs should now be resolved.As part of the release, all of our SDKs now fully support CIM, ARB, eCheck.Net, Card Present and the Transaction Details API. To review the available SDKs, please visit http://developer.authorize.net/downloads/.

We have also added a page on the Developer Center for information on our Transaction Details API located at http://developer.authorize.net/api/transaction_details/. Here you can download the SDKs or review the XML and SOAP API guides.Our Test Account Error Generation Guide is now also available from our Troubleshooting Tools page at http://developer.authorize.net/tools/.

And last, if you need a Card Present test account, you can now request one from our test account page at https://developer.authorize.net/testaccount/. Just make sure that Card Present is checked.Thanks and we hope these updates will help you as you go about your integrations and testing.

 

Apr
08

Welcome to the Community!

Welcome to the Authorize.Net Developer Community. The purpose of this community is to provide a peer-to-peer support and interaction channel for developers using Authorize.Net’s APIs, certification and affiliate programs.

To be part of our community, there are some guidelines to which we expect you to adhere. Nothing crazy – just the basic, should-go-without-saying kind of stuff that we actually do need to say.

Authorize.Net Developer Community Guidelines
First and foremost, to register for an account on the Developer Community, you will need to agree to our Terms of Use and Privacy Policy. We strongly recommend that you read these thoroughly as your community membership is at all times contingent on your adhering to both of them.

The following community guidelines are intended to help foster helpful community interaction and in some cases are already covered in the Terms of Use and Privacy Policy. But because they are so important for a successful community, we’re listing them again:

  • Be nice and courteous to everyone. Seriously. If you can’t play nice with the others, then you won’t be playing at all.
  • Be professional and respectful. Everyone has something to offer. You may not agree with everyone or think every message adds value, but that doesn’t give you the right to start acting like a teenager. Any posts that contain profanity; material that is libelous, fraudulent, vulgar or obscene, indecent, lewd, harassing, pornographic, abusive, offensive, defamatory, threatening, hateful, inflammatory, or otherwise objectionable; or attacks on other users, will be removed and you run the risk of being banned from the community.
  • Be relevant and concise. Stay on topic and add value. Don’t post just for the sake of posting. If you post, your comments should be relative to the topic at hand, and be straight and to the point. Those reading your posts shouldn’t be taken on a trip through la-la-land before finally figuring out what you’re talking about.
  • Be careful. Remember, as a peer-to-peer community, this is user-generated content. You’ll find great advice here, but your particular integration probably varies a bit from those giving the advice. It’s even possible that some posts contain information that is flat-out wrong. Use the same good judgment in our community that you would use on information pulled from anywhere else on the Internet.
  • Do not send SPAM or use the community for your personal commercial use. Don’t be that guy. No one likes him. Really, they don’t.
  • Respect the moderators and the job they do. Every member of the Developer Community is responsible for doing their part to foster an open and inviting community. If you see inaccurate, off-topic, or disruptive posts, you should report them to the moderators.

And last but not least…

  • Have fun. Sure, this may be “work” for all of us, but that doesn’t mean it can’t be fun and entertaining at the same time. As your community administrators and moderators, we can assure you that we’re expecting to have some fun as well—or at the very least, not be bored to tears.

The Community Guidelines were created so that you know what is expected of you and what you can expect from other members. We want the community to be friendly, informative and fun for all. If at any time you have questions about the community, please ask! Our moderators and administrators are always happy to help.

And now that we’ve gotten that out of the way, we hope you’ll enjoy the community!

 

Apr
06

Latest Developer Center Release Complete

Our latest Developer Center release is now complete. Any of the bugs or errors reported to us concerning the SDKs should now be resolved.

As part of the release, all of our SDKs now fully support CIM, ARB, eCheck.Net, Card Present and the Transaction Details API. To review the available SDKs, please visit http://developer.authorize.net/downloads/.

We have also added a page on the Developer Center for information on our Transaction Details API located at http://developer.authorize.net/api/transaction_details/. Here you can download the SDKs or review the XML and SOAP API guides.

Our Test Account Error Generation Guide is now also available from our Troubleshooting Tools page at http://developer.authorize.net/tools/. And last, if you need a Card Present test account, you can now request one from our test account page at https://developer.authorize.net/testaccount/. Just make sure that Card Present is checked.  Thanks and we hope these updates will help you as you go about your integrations and testing.

 

 

Apr
06

Settlement Changes in Test Accounts

In the past, when using a test environment account, transactions would only settle about every 10 minutes and settlement did not occur by default. Instead you had to email developer support with your test account Login ID asking that settlement be initiated.

This is no longer the case. With the changes that were recently implemented on the Developer Center, all test environment accounts are now automatically settling transactions without any action required on your part. There is no longer a need to request that settlement be enabled in order to refund transactions in your test account.

Also, transactions are now settling only once per day after the Transaction Cut-Off Time in the account. Please note that a settlement file will only run once per day. If you change the Transaction Cut-Off Time in the account to try to force a settlement to occur, this will likely only cause delays in your next 1-2 settlement files.

 

 

Apr
06

New XML API for Transaction Processing

Hi again,

Today, we’re also pleased to announce that we now have an XML API for Transaction Processing. The API, createTransactionRequest, is available now. The guide is still being finalized, but you can review the XSD at https://api.authorize.net/xml/v1/schema/AnetApiSchema.xsd.

And of course, for your convenience, here are the XML examples for the request and response:
———————————————————————
The following is the XML sent for transactions.
———————————————————————
Read the rest of this entry »

Older posts «