FAQ

Overview and Terminology

“Sign on” vs “sign up”

With Noca, there’s no such thing as a user “sign up” process. If you’re a new user, we present a SecureCheck image with empty account details. When you fill them out and submit the check, you’re signed up.

Authentication

Your users are our users. As a Noca merchant, you’re responsible for authenticating the user. If you send us a payment saying “joeusername” is making a payment, we require that you have authenticated “joeusername”. We internally store whether “joeusername” has used our service from your site before, and are therefore able to provide a completely transparent sign-on.

In the case above, “joeusername” is the OCPformMerchantCustomerIdentity. This value must be unique for each user on your site: typically, it would be a username. This value should not change over time, and should never be shared between multiple users at your site.

Multiple sites

Persons paying by Noca through different Noca merchants typically have their accounts automatically linked by our system, and we’ll be providing a manual way to do this in the future. The OCPformMerchantCustomerIdentity is really a link between a merchant’s system and ours – multiple merchantCustomerIdentities point to a single Noca user.

The Basics

What browsers are supported?

All browsers can use Noca’s payment methods. If your browser does not perform correctly, you may not have Javascript enabled in your browser.

What does a valid Routing Number look like?

Routing numbers are defined by the American Bankers Association, and have a specific mathematical formula, which we check (see http://en.wikipedia.org/wiki/Routing_transit_number). A good number to use for testing is a bank in Texas with an easy-to-remember number: 111000025.

What fields need to be unique?

Many problems clients face during integration stem from using the same credentials again and again. Here are some tips:

• Maintain a 1:1 mapping between merchantCustomerIdentity and email. Don’t assign the same email to different customers.
• Use a new email and merchantCustomerIdentity when you want to test as a new user; use older credentials to test as a preexisting customer.

What went wrong?

Ensure you always set a ReplyTo value. If you don’t set OCPformReplyTo, we can’t post an error response to your site. There are two values you’ll want to look at when something goes wrong:

• status – a code indicating generally where the fault occurred (see the API guide)
• statusText – a description of the error. This field will generally state what input caused the error. Example:
  Failed  to create invoice: com.noca.persistence.ValidationException [Missing  required value]Missing required value: Invoice/TotalAmount

What fields are required?

The API guide describes which fields are required. In addition to the 11 fields which are always required, there are also *sets* of variables which must either ALL be submitted or not submitted at all.

Why does it say a field was not submitted when I actually submitted it?

Ensure all OCPform variables are sent as strings. OCPformTotalAmount = 15.00, for example, will not work.

Web Services

What is my username?

Your username is your merchant ID. Example: 152

What is my API key?

Your API key is different for Sandbox and Production. It is available from the Merchant Portal. Example: 7d408814-9a77-4287-bbf3-1e69472d130b

I have authentication errors

Ensure you have set PasswordType to PasswordText instead of the default, PasswordDigest.

What are “MustUnderstand” W3 Addressing errors?

Our present implementation does not use WS-Addressing functionality, and requests containing an XML-SOAP “MustUnderstand” flag will fail. You should be able to configure your client to either not set ‘MustUnderstand’ or not send the WS-Addressing headers.

The answer to my question isn’t here.

Email support@noca.com or leave a comment below.