Skip to main content

Documentation Index

Fetch the complete documentation index at: https://bancofcalifornia-preview.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

We have designed our gateway to be able to handle transaction submissions and responses in the Authorize.Net format. We call this our Gateway Emulator. To use the Gateway Emulator, your shopping cart or application must support the Authorize.Net AIM or SIM method of integration. If the application supports the AIM or SIM method, you simply need to change the transaction POST URL to our Gateway Emulator URL. The Gateway does not support the emulation of XML AIM, CIM, ARB, DPM, Card Present or Transaction Details APIs. Our Gateway Emulator URL is:
AIM:https://gateway.bancedge.com/gateway/transact.dll
SIM:https://gateway.bancedge.com.com/cart/ausi.php
You will need to change any production and test Authorize.Net URLs to one of the above URLs. The following URLs should be replaced:
https://secure.authorize.net/gateway/transact.dll
https://test.authorize.net/gateway/transact.dll
Some applications will not contain the test URL. In that case, you will only be changing one URL. Once you have updated the URLs to point to us, the application will submit transactions without needing changes to the code base. You will then need to configure the Authorize.Net AIM or SIM payment module with the following credentials:
  • API ID or Login ID is your gateway username.
  • Transaction Key is your gateway password.
  • The MD5 Hash is the word “gateway” without the marks.
For testing, you can use the username and password of “demo” and “password”. CIT/MIT is supported even though the official AIM API does not support it. Please use the variable names and values documented under the Payment API on all relevant transactions.

​
Authorize.Net Modern XML Emulator

If your application is using Authorize.Net’s current XML API, then you can connect using our newest emulator. Like the above-mentioned emulators, this will accept requests in the same XML format that Auth.Net would accept, so it’s just a matter of changing your POST URL to the one below and using your gateway credentials for authentication. This emulator also emulates the response so that should look the same to your software. Our Modern XML Emulator URL is:
https://gateway.bancedge.com/api/transrequest.php
For authentication, this API looks for “name” and “transactionKey”.
  • “name” can be anything, as it is not used for authentication.
  • “transactionKey” is your API Security Key.

​
Sparrow

If your application is using SparrowOne’s Services API, you can connect your software to the gateway via this emulator. Simply replace the POST URL in your software to the following address and you can submit transactions, add update, and delete Customer Vault IDs, and create recurring subscriptions.
https://gateway.bancedge.com/api/spar.php
Authentication uses your merchant account’s API Security Key in the ‘mkey’ variable.