TokenEx Labs: ActiveMerchant Integration, New API Functions

We are now utilizing the ActiveMerchant library, (, for connecting to ActiveMerchant supported payment gateways. Making use of ActiveMerchant in our environment was a bit of an interesting challenge since it is a Ruby program and we run .Net almost exclusively. However, we have overcome these challenges quite creatively.  Our solution includes wrapping ActiveMerchant into Sinatra RESTful web service and making the connections from our .Net code to Ruby over HTTP POSTs.  So far, so good!

Also, ActiveMerchant is to be a great solution for rapid deployment of new gateways as development and testing time to wrap a new gateway takes less than a day.  Considering our business model of supporting multiple processors and payment gateways, this means your company can move in between any supported processor or payment gateway in a very short amount of time.

We would also like to announce the release of a few new API functions for your consumption:

  • configureMerchant allows you to setup and modify your gateway on the fly. This function also allows you to modify the list of acceptable IP addresses that can connect to TokenEx using your account.
  • tokenizeString allows you to tokenize any arbitrary string. A fairly obvious use for this API is the tokenization of serialized data. Perhaps you want to store billing information on our platform. You could place all that data into a JSON object and tokenize that entire customer.  (Note: A fee will be charged for every 32 megabytes stored using this feature.)
  • tokenizeBytes is a very exciting feature. You can tokenize any arbitrary byte array up to 500 megabytes in length, meaning you can tokenize pretty much any document you would like.  (Note: A fee will be charged for every 32 megabytes stored using this feature.)
Topic(s): payments , PCI DSS , tokenization

Keep Up With Our PCI & Privacy Blog