Testing ‹ Noca

This page provides an increasing body of knowledge to assist developers with the testing and integration process.

Environment

All testing should take place on the Sandbox environment. Tests on sandbox are never settled and do not reach a bank. No testing should take place on production, and any “tests” on production are binding.

Values returned (POSTed) to “replyTo” URL

For Merchants

merchantIdentity
Has the value that was in the OCPformMerchantCustomerIdentity variable.

transactionID
Internal Noca transaction reference.

statusText
Describes the result of the transaction. A return starting with “HOLD” indicates that the transaction is over $25 or that the user is attempting a second transaction without verifying their account (the transaction will be put on hold in this case).

merchantReference
Returns the string that was in the OCPformInvoiceID variable.

currency
Returns the three letter identifier of the currency used.

status
Integer that describes the status of the transaction.

Status	Description
0	Success
1	Client error
2	User error
3	Server error
4	Session error

invoiceID
Internal Noca invoice reference.

totalAmount
The total amount that was charged. A malicious user can change this so it should only be used for temporary verification.

For Marketplaces

merchantIdentifier
How the Marketplace uniquely identifies the Merchant.

merchantID
The identity of the merchant in Noca’s system–used for identifying the merchant when customers make payments.

Common Questions or Issues

The check image does not load.

You’re probably not sending a valid set of variables. The OCPform variables can be quite stringent – do a review of what you’re sending and ensure that ALL required fields have a value.

In particular, make sure you set the InvoiceID and the MerchantID. Also make sure that within your contact information, you specify the OCPformContactInformationSalutation field! It’s easily missed.

I submit the check but nothing happens!

This is most likely because of duplicate entries in the system. When you’re doing a lot of repeated testing, we get unusual data such as half-completed requests and multiple registration attempts from the same email or MerchantIdentity.

If we’re returning a 500 Server Error or the check just doesn’t submit, the best course of action would be try clearing your browser’s cache and use a fresh email and MerchantIdentity combination. Also make sure you enter a fresh AccountNumber, as we don’t allow these items to conflict in our system.