Bambora North America (formerly Beanstream) gateway guide
Additional notes |
---|
If you’d like to use a dynamic descriptor, contact Beanstream technical support to add Dynamic DBA to your account. Use ref1 as part of your DBA Suffix. ref1 can be passed in as a gateway specific field. |
Adding a Bambora North America gateway
To add a Bambora North America gateway:
curl https://core.spreedly.com/v1/gateways.xml \
-u 'C7cRfNJGODKh4Iu5Ox3PToKjniY:4UIuWybmdythfNGPqAqyQnYha6s451ri0fYAo4p3drZUi7q2Jf4b7HKg8etDtoKJ' \
-H 'Content-Type: application/xml' \
-d '<gateway>
<gateway_type>beanstream</gateway_type>
<merchant_id>23423423</merchant_id>
<username>username</username>
<password>password</password>
<api_key>Api Key</api_key>
</gateway>'
<gateway>
<token>BQ1bfiMFcxrHxl3NE5YfKhYsQXD</token>
<gateway_type>beanstream</gateway_type>
<name>Bambora (formerly Beanstream)</name>
<description nil="true"/>
<merchant_id>23423423</merchant_id>
<username>username</username>
<characteristics>
<supports_purchase type="boolean">true</supports_purchase>
<supports_authorize type="boolean">true</supports_authorize>
<supports_capture type="boolean">true</supports_capture>
<supports_credit type="boolean">true</supports_credit>
<supports_general_credit type="boolean">false</supports_general_credit>
<supports_void type="boolean">true</supports_void>
<supports_verify type="boolean">true</supports_verify>
<supports_reference_purchase type="boolean">false</supports_reference_purchase>
<supports_purchase_via_preauthorization type="boolean">false</supports_purchase_via_preauthorization>
<supports_offsite_purchase type="boolean">false</supports_offsite_purchase>
<supports_offsite_authorize type="boolean">false</supports_offsite_authorize>
<supports_3dsecure_purchase type="boolean">false</supports_3dsecure_purchase>
<supports_3dsecure_authorize type="boolean">false</supports_3dsecure_authorize>
<supports_store type="boolean">false</supports_store>
<supports_remove type="boolean">false</supports_remove>
<supports_fraud_review type="boolean">false</supports_fraud_review>
<supports_disburse type="boolean">false</supports_disburse>
</characteristics>
<credentials>
<credential>
<name>merchant_id</name>
<value>23423423</value>
</credential>
<credential>
<name>username</name>
<value>username</value>
</credential>
</credentials>
<gateway_specific_fields>
<gateway_specific_field>ref1</gateway_specific_field>
<gateway_specific_field>shipping_email</gateway_specific_field>
<gateway_specific_field>recurring</gateway_specific_field>
</gateway_specific_fields>
<payment_methods>
<payment_method>credit_card</payment_method>
</payment_methods>
<state>retained</state>
<redacted type="boolean">false</redacted>
<created_at type="dateTime">2018-07-18T13:36:14Z</created_at>
<updated_at type="dateTime">2018-07-18T13:36:14Z</updated_at>
</gateway>
Third-party 3DS2 auth data
Spreedly will automatically handle the field mapping for sending third-party 3DS2 authentication data to Beanstream. For more information about how to use this feature, see the 3DS2 Third-party Authentication Guide. Spreedly fields map to the relevant Beanstream fields as described in the following table. Please see check Beanstream API docs for detailed descriptions of each of these fields and when to use them.
Spreedly field | Bambora North America (Beanstream) field |
---|---|
ecommerce_indicator | SecureECI |
authentication_value | SecureCAVV |
directory_server_transaction_id | SecureXID |
xid | SecureXID |
Gateway specific fields
When interacting with a Bambora North America gateway to run transactions, you can add ref1
as a gateway specific field. This can be used to pass in a dynamic descriptor for the transaction. Your account needs to be setup for Dynamic DBA for this to work correctly. Contact Bambora North America gateway technical support to set it up. Make sure ref1
is part of the DBA Suffix.
If you would like to make a recurring charge, you will need to send the recurring
field with a value of true
. This will skip CVV validation in your request.
shipping_email
may also be specified.
curl https://core.spreedly.com/v1/gateways/LlkjmEk0xNkcWrNixXa1fvNoTP4/purchase.xml \
-u 'C7cRfNJGODKh4Iu5Ox3PToKjniY:4UIuWybmdythfNGPqAqyQnYha6s451ri0fYAo4p3drZUi7q2Jf4b7HKg8etDtoKJ' \
-H 'Content-Type: application/xml' \
-d '<transaction>
<payment_method_token>56wyNnSmuA6CWYP7w0MiYCVIbW6</payment_method_token>
<amount>100</amount>
<currency_code>USD</currency_code>
<gateway_specific_fields>
<beanstream>
<ref1>Dynamic Descriptor</ref1>
<recurring>true</recurring>
<shipping_email>[email protected]</shipping_email>
</beanstream>
</gateway_specific_fields>
</transaction>'
<transaction>
<on_test_gateway type="boolean">true</on_test_gateway>
<created_at type="dateTime">2017-10-13T17:51:23Z</created_at>
<updated_at type="dateTime">2017-10-13T17:51:23Z</updated_at>
<succeeded type="boolean">true</succeeded>
<state>succeeded</state>
<token>JIeSCs7FcOsx1zO06eGfSXLjLWj</token>
<transaction_type>Purchase</transaction_type>
<order_id nil="true"/>
<ip nil="true"/>
<description nil="true"/>
<email nil="true"/>
<merchant_name_descriptor nil="true"/>
<merchant_location_descriptor nil="true"/>
<gateway_specific_fields>
<beanstream>
<ref1>Dynamic Descriptor</ref1>
<recurring>true</recurring>
<shipping_email>[email protected]</shipping_email>
</beanstream>
</gateway_specific_fields>
<gateway_specific_response_fields>
</gateway_specific_response_fields>
<gateway_transaction_id>52</gateway_transaction_id>
<gateway_latency_ms type="integer">23</gateway_latency_ms>
<amount type="integer">100</amount>
<currency_code>USD</currency_code>
<retain_on_success type="boolean">false</retain_on_success>
<payment_method_added type="boolean">false</payment_method_added>
<message key="messages.transaction_succeeded">Succeeded!</message>
<gateway_token>T11bJAANtTWnxl36GYjKWvbNK0g</gateway_token>
<shipping_address>
<name>Newfirst Newlast</name>
<address1 nil="true"/>
<address2 nil="true"/>
<city nil="true"/>
<state nil="true"/>
<zip nil="true"/>
<country nil="true"/>
<phone_number nil="true"/>
</shipping_address>
<response>
<success type="boolean">true</success>
<message>Successful purchase</message>
<avs_code nil="true"/>
<avs_message nil="true"/>
<cvv_code nil="true"/>
<cvv_message nil="true"/>
<pending type="boolean">false</pending>
<result_unknown type="boolean">false</result_unknown>
<error_code></error_code>
<error_detail nil="true"/>
<cancelled type="boolean">false</cancelled>
<fraud_review nil="true"/>
<created_at type="dateTime">2017-10-13T17:51:23Z</created_at>
<updated_at type="dateTime">2017-10-13T17:51:23Z</updated_at>
</response>
<api_urls>
</api_urls>
<payment_method>
<token>1rpKvP8zOUhj4Y9EDrIoIYQzzD5</token>
<created_at type="dateTime">2017-06-26T17:04:38Z</created_at>
<updated_at type="dateTime">2017-10-13T17:37:45Z</updated_at>
<email>[email protected]</email>
<data>
<my_payment_method_identifier>448</my_payment_method_identifier>
<extra_stuff>
<some_other_things>Can be anything really</some_other_things>
</extra_stuff>
</data>
<storage_state>retained</storage_state>
<test type="boolean">true</test>
<last_four_digits>1111</last_four_digits>
<first_six_digits>411111</first_six_digits>
<card_type>visa</card_type>
<first_name>Newfirst</first_name>
<last_name>Newlast</last_name>
<month type="integer">3</month>
<year type="integer">2032</year>
<address1 nil="true"/>
<address2 nil="true"/>
<city nil="true"/>
<state nil="true"/>
<zip nil="true"/>
<country nil="true"/>
<phone_number nil="true"/>
<company nil="true"/>
<full_name>Newfirst Newlast</full_name>
<eligible_for_card_updater nil="true"/>
<shipping_address1 nil="true"/>
<shipping_address2 nil="true"/>
<shipping_city nil="true"/>
<shipping_state nil="true"/>
<shipping_zip nil="true"/>
<shipping_country nil="true"/>
<shipping_phone_number nil="true"/>
<payment_method_type>credit_card</payment_method_type>
<errors>
</errors>
<verification_value></verification_value>
<number>XXXX-XXXX-XXXX-1111</number>
<fingerprint>e3cef43464fc832f6e04f187df25af497994</fingerprint>
</payment_method>
</transaction>
Gateway specific response fields
A response from Bambora North America gateway may contain an auth_code
field which you can find in the gateway_specific_response_fields
. For example, a transaction could have something like this:
<transaction>
<token>LgpTNGjsWQs9DwdxcbreUVz0R8p</token>
<transaction_type>Purchase</transaction_type>
<gateway_specific_response_fields>
<beanstream>
<auth_code>abc123</auth_code>
</beanstream>
</gateway_specific_response_fields>
</transaction>
To request any gateway_specific_fields
or gateway_specific_response_fields
, please contact Support with your request and the gateway documentation for the fields of interest.
Updated 5 months ago