Bambora Checkout

The Bambora Checkout Hosted Payment configuration allows administrators to process secure online transactions through a fully integrated Bambora (Wordline) merchant account. Its primary purpose is to enable reliable payment processing and tokenized profiles directly within the OPS-COM checkout flow by utilizing secure authorization headers. This article is intended for OPS-COM administrators.

Setup and Configuration

To properly configure your Bambora/WordlineBambora payment type in OPSCOMOPS-COM, you will require two separate "Authorizationencoded Headers".authorization Theseheaders: headersthe will be referenced below as:

Payment Authorization Header
Profile Authorization Header

The process to generateand the twoProfile differentAuthorization encodedHeader. headers is similar in that bothBoth require your Bambora Merchant ID +(MID) and a specific API access passcode,passcode to generate.

Generating the Payment Authorization Header

1. Log in to your Bambora account.

2. Select Administration, click Account Settings, and boththen areselect encodedOrder atSettings from the sameleft link,navigation howevermenu.

3. Scroll down to the API access passcode is different for each and shown on different pages in Bambora (order settings vs payment profile configuration).section.

   Bambora

Configuration:

4. Order Settings:

   Login to your Bambora account, then on Click the left navigation select Administration → Account Settings → Order Settings.

   API access passcode (Payment Authorization Header):

   On the Order settings page scroll down to "API access passcode". If there is nothing in the API access passcode field click the "Generate New Code" button.button Afterif generatingthe yourfield APIis accessempty.

   passcode
make
5. sure

   Click tothe scrollUpdate downbutton toat the bottom of the page and click "Update" to save your changes.

   Merchant

ID (MID):

Your Merchant ID can be found in the top right of your Bambora account.

Encode API Passcode (Payment Authorization Header):

Navigate

	Now that you know your API access passcodeLocate and Merchant ID go here. Copy and pastecopy your Merchant ID (1) and API access passcode (2) into the appropriate fields, then click "Encode"(3).   Copy/record the Payment Authorization Header shown. This will be needed later when you setup the Bambora Checkout payment type in OPSCOM. It will be referenced further down this page as the Payment Authorization Header. You should temporarily paste this into a program such as Notepad for easy access later since you will need it later during the OPSCOM configuration.   You will want to make sure to copy only the following section returned (excluding quotation marks): "Passcode ______" For example, select/copy as shown in the highlighted example below, starting at the P on Passcode.  We want to exclude/not copy "Authorization:"
Similar to the above process for encoding your Payment Authorization Header, we will be going through a similar process for encoding your Profile Authorization Header. Payment Profile Configuration:
	Login to your Bambora account, then on the left navigation select Configuration → Payment Profile Configuration.
API access passcode (Profile Authorization Header): Under Security Settings make sure "API access passcode:" is selected. If there is nothing in the API access passcode field click the "Generate New Code" button. After generating your API access passcode make sure to scroll down to the bottom of the page and click "Update" to save your changes.
Merchant ID (MID):
	Your Merchant ID can be found infrom the top right of your Bambora account.
to Encodethe Bambora encoding tool URL provided by your implementation specialist. Paste your Merchant ID and the new API access passcode into the appropriate fields. Click the Encode button. Copy the generated Payment Authorization Header. Ensure you only copy the string starting with the word Passcode (e.g., Passcode MzAw...). Do not copy the Authorization: prefix or the quotation marks. Generating the Profile Authorization Header):
	NowSelect thatConfiguration youand knowclick yourPayment Profile Configuration from the left navigation menu in Bambora. Ensure the API access passcode andoption Merchantis IDselected go here.. Copy and paste your Merchant ID (1) and API access passcode (2) intounder the appropriateSecurity fields,Settings then click "Encode"(3).section.   Copy/recordClick the AuthorizationGenerate PasscodeNew returned.Code Thisbutton will be needed later when you setupif the Bamborafield Checkoutis paymentempty. type in OPSCOM. It will be referenced further down this page as Click the "Profile Authorization Header". You should temporarily paste this into a program such as Notepad for easy access later since you will need it later during the OPSCOM configuration.   You will want to make sure to copy only the following section returned (excluding quotation marks): "Passcode ______" For example, select/copy as shown in the highlighted example below, starting at the P on Passcode.  We want to exclude/not copy "Authorization:"

---

OPSCOM Configuration:

specificProfileAPIfromtheProvider

Create new Payment Type in OPSCOM:
	Login to your OPSCOM system with an administrator account that has permission to edit payment types.   In the OPSCOM menu select System Configuration → Payments → Setup Payment Types → Add Type.   Select "Bambora - Checkout" from the Provider list, then click "Next Step".
Edit Payment Type - Enabled for User Types:
	Type Name: The Type Name can be whatever you want it to be, though please note this will also be the name displayed to users during payment checkout when they are prompted to select a payment method.   You can reference the specific hosted payment provider or something more generic such as "Online Credit Card Payment", "Online payment", "Credit Card", etc. Really it's up to you and what you think makes most sense to your site users when making a payment.   Enabled for User Types: Select the User Types you wish this new Payment Type to be visible to so they can select it during payment checkout. You can change these user types at any time.   Once done make sure to click the "Update Payment Type" button at the bottom of the page to save your changes. Navigate back to the Bambora encoding tool. Paste your Merchant ID and this page.
access Editpasscode into the appropriate fields. Click the Encode button. Copy the generated Profile Authorization Header, again ensuring you only copy the string starting with the word Passcode. Use a Text Editor: Temporarily paste your generated headers into a program like Notepad while switching between Bambora and OPS-COM. This ensures you do not lose the copied strings during the multi-step configuration process. Adding the Payment Type in OPS-COM Hover over System Configuration and click Payments then Setup Payment Types. Click the Add Type button. Select Bambora - Settings:Checkout
list. Click the Next Step button.	Enter a clear, descriptive name into the Type Name field (e.g., Online Credit Card Payment). Select the specific user groups who should have access to this method from the Enabled for User Types list. Enable or disable the checkboxes for Enable for Text2ParkMe: if, you aren't using this module leave the button unchecked. Enable for for Permit Renewal Payments: if, youand aren'tEnable usingfor thisGuest featurePayments leavebased on your operational needs. Select Billing Details from the button unchecked. Enable for Guest Payments: if you aren't using this feature leave the button unchecked.   Prompt Information: Thisdrop-down dependsmenu onif whetheryou or not you'reare enforcing AVS (Address Verification Service) in your Bambora account.account, Thisor is set in Bambora underselect AdministrationEmail Address → Account Settings → Order Settings → Transaction Reversal Options Conditions. If using AVS  you will require the Prompt for to have "Billing Details" selected, which will prompt users to supply their billing address information during checkout so AVS can pass. Otherwise if AVS isn'tis not required. Paste your copied headers into the Profile Authorization Header and Payment Authorization Header fields under the Production Credentials section. Enable the Validate Card when adding subscriptions checkbox if you want the card validated immediately by the payment provider when it is first added as a subscription method in a user's profile. Leave the Phone Number Field set to hidden unless specifically required inby your fraud detection settings. Click the Update Payment Type button at the bottom of the page to save your configuration. AVS and Prompt Settings Match: You must align your OPS-COM prompt information with your Bambora accountAVS settings. If Address Verification Service (AVS) is enabled in Bambora, you canmust selectset OPS-COM to prompt for Billing Details. If you only prompt for Email Address inwhile whichAVS caseis noactive, address informationtransactions will befail requiredto fromprocess. Using this Feature Because this is a backend payment gateway configuration, administrators do not manually interact with this feature on a daily basis. Once fully configured, the Bambora Checkout integration automatically handles electronic routing and card tokenization when users makingprocess payments.transactions on the user portal or when administrators process manual credit card payments via the administrative portal.   Best Practices and Considerations AVS Configuration: If using AVSAVS, Bambora recommends enabling only the “AVS Postal/Zip Code Mismatch”Mismatch option. as theThe Street Mismatch option is extremely sensitive and may result in a high declinerate rate.of declined payments due to minor formatting typos.   Production Credentials:   User-Friendly Naming: The text you enter into the ProfileType AuthorizationName Header:field Copyis exactly what your users will see when selecting a payment method during checkout. Choose a generic and pasterecognizable name, such as "Credit Card", to avoid confusion during the Profilecheckout process. Authorization Header into this field as detailed in the steps above.   Example: Passcode MzAwMjZ0NDVxOkY0NRg0MkRDQkM4QTQxNTJCMTM1MUE4OAZxN0NCM4ND Payment Authorization Header: Copy and paste the Payment Authorization Header into this field as detailed in the steps above.   Example: Passcode BVSTYjZ0NDVxLkY0NRg0MURDQkM5QTQxNTJCMTM1HUE3OBQxN0NBN8VC Other Settings: Validate Card when adding subscriptions: Optional setting related to when/if users add a subscription method in OPSCOM for this payment type and whether or not the card is validated by the payment provider when first added as a subscription method. If left unchecked the card will only be validated when/if used for a payment.   Phone Number Field: Usually hidden, but some payment providers may require a phone number for payments depending on your fraud detection settings. Recommend leaving hidden unless otherwise stated by your payment provider or if you check a setting in Bambora to require a phone number.
	Make sure to click the "Update Payment Type" button at the bottom of the page.