2Checkout.com » language http://www.2checkout.com/community merchant account / credit card processing alternative Tue, 16 Mar 2010 13:29:45 +0000 http://wordpress.org/?v=2.9.1 en hourly 1 Reviewing 2009 and Looking Forward to 2010 http://www.2checkout.com/community/blog/2checkout-blog/reviewing-2009-and-looking-forward-to-2010 http://www.2checkout.com/community/blog/2checkout-blog/reviewing-2009-and-looking-forward-to-2010#comments Fri, 01 Jan 2010 14:07:06 +0000 bion http://www.2checkout.com/community/?p=2783 It’s that time again, time to remember the passing year and make plans for the next. Looking back on the year I am happy that our first improvement was the addition of 14 languages to our purchase page. Making purchasing products easier for your customers has been a continuing theme that we will continue in the coming year.

This year many of our projects have been the direct result of your feedback and requests. One request we get regularly is the addition of supported currencies. In October, we added the Argentina Peso (ARS), Brazilian Real (BRL), Indian Rupee (INR), Mexican Peso (MXN), and the South African Rand (ZAR) to our list of supported currencies.

In May we launched a new way for your customers to make purchases. Our PIN-Debit payment option is the first software-only service of its kind in the U.S. Through PaySecure’s encrypted software, your customers who prefer to use PIN debit, or have PIN-only debit cards can buy using their debit card and their 4-digit ID. This is just one more way we are making shopping online easier and more accessible to people all over the world.

These are in addition to our Beta API release (which should be released soon), improved navigation within our vendor area, and numerous fixes and modifications that have been a direct response to your feedback. We appreciate all the comments and feedback we receive. I want to thank all of you who have offered suggestions over the past few years – your needs and ideas are a large part of what informs our decisions.

Speaking of the Beta API, our API has been one of the biggest projects we have undertaken. Based on your requests and our beta-tester’s feedback, we have been developing and finalizing the API. Look for some good news in early 2010.

We are also continuing to make our vendor area as useful and easy to navigate as possible. We have more big plans, and some equally big announcements for next year. We will be focused on giving you easier access to more tools and more information, and more options for both you and your customers. I really wish I could be more specific, because I’m excited about every one of these projects…but I need to leave you with some surprises for the new year!

What a year 2009 has been and what a year 2010 will be!

]]> http://www.2checkout.com/community/blog/2checkout-blog/reviewing-2009-and-looking-forward-to-2010/feed 1 Special characters must be UTF-8 encoded http://www.2checkout.com/community/blog/knowledge-base/suppliers/tech-support/multi-language-options/special-characters-must-be-utf-8-encoded http://www.2checkout.com/community/blog/knowledge-base/suppliers/tech-support/multi-language-options/special-characters-must-be-utf-8-encoded#comments Wed, 07 Jan 2009 23:05:12 +0000 2checkout http://www.2checkout.com/community/blog/uncategorized/special-characters-must-be-utf-8-encoded/  All 2Checkout purchase routines require that any special “non-ASCII characters” (i.e. à, å) passed in as parameter values are UTF-8 encoded. This means that any special characters that are not encoded properly will not be interpreted or displayed correctly by our system. For example, if you pass in ‘à la clientele confidentialité’ as the card_holder_name, the purchase routine will display it as ‘? la client?le confidentialit?’. These characters need to be UTF-8 encoded when they are passed into our purchase routine so our system will accept it. If the special characters are UTF-8 encoded ‘%C3%A0%20la%20clientele%20confidentialit%C3%A9′ instead of ‘à la clientele confidentialité’, our system interprets the special characters correctly. Please note that this will not affect customers as these special characters can be entered normally in the information fields on purchase screens, it’s only when the characters are part of a purchase URL that they need to be UTF-8 encoded.

Characters passed in incorrectly.

https://www.2checkout.com/checkout/purchase?card_holder_name=
à la clientele confidentialité&street_address=1785+Obrien+Rd&city=Columbus&state=
Ohio&zip=43228&country=United+States&phone=6149212450&email=no-reply@2co.com&sid=
XXXXXX&product_id=1&quantity=1

Purchase routine display in IE7:
Unencoded IE7

Purchase routine display in Firefox:
Unencoded Firefox

Characters passed in correctly.

https://www.2checkout.com/checkout/purchase?card_holder_name=
%C3%A0%20la%20clientele%20confidentialit%C3%A9&street_address=1785+Obrien+Rd&city=
Columbus&state=Ohio&zip=43228&country=United+States&phone=6149212450&
email=no-reply@2co.com&sid=XXXXXX&product_id=1&quantity=1

Purchase routine display in IE7 and Firefox:
encoded Firefox

]]> http://www.2checkout.com/community/blog/knowledge-base/suppliers/tech-support/multi-language-options/special-characters-must-be-utf-8-encoded/feed 0