BridgePay Gateway Guide

close

Services and Compatibility

Payment Gateway Company Name:
BridgePay Network Solutions
Services that work with Spreedly:
  • BridgePay
Supported operations:
Purchase, Authorize, Capture, Refund, Void, Verify, Store
Supported payment types:
Credit Card, Bank Account
Regions:
North America

Authentication and Security

Specific names for credentials:
User Name, Password

Onboarding Merchants in:

Adding

To add a BridgePay gateway:


curl https://core.spreedly.com/v1/gateways.xml \
  -u 'Ll6fAtoVSTyVMlJEmtpoJV8S:RKOCG5D8D3fZxDSg504D0IxU2XD4Io5VXmyzdCtTivHFTTSy' \
  -H 'Content-Type: application/xml' \
  -d '<gateway>
        <gateway_type>bridge_pay</gateway_type>
        <user_name>user_name</user_name>
        <password>password</password>
      </gateway>'

<gateway>
  <token>S88DGQUFLMytZsGn9uKlz1sQdY9</token>
  <gateway_type>bridge_pay</gateway_type>
  <name>BridgePay</name>
  <description nil="true"/>
  <user_name>user_name</user_name>
  <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">true</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>user_name</name>
      <value>user_name</value>
    </credential>
  </credentials>
  <gateway_specific_fields>
  </gateway_specific_fields>
  <payment_methods>
    <payment_method>credit_card</payment_method>
    <payment_method>bank_account</payment_method>
    <payment_method>third_party_token</payment_method>
  </payment_methods>
  <state>retained</state>
  <redacted type="boolean">false</redacted>
  <created_at type="dateTime">2016-08-11T17:14:15Z</created_at>
  <updated_at type="dateTime">2016-08-11T17:14:15Z</updated_at>
</gateway>


env = Spreedly::Environment.new('Ll6fAtoVSTyMlJEm', 'RKcG5D8D3fZxDSg504U2XD4Io5VXz')
env.add_gateway(:bridge_pay, user_name: 'user_name', password: 'password')


#<Spreedly::Gateway:0x007fb5db8628e0
 @created_at="2016-08-11T17:14:16Z",
 @credentials={"user_name"=>"user_name"},
 @gateway_type="bridge_pay",
 @name="BridgePay",
 @state="retained",
 @token="ChttPRR9rSDhkVszzhU76RnlurL",
 @updated_at="2016-08-11T17:14:16Z">

Gateway specific response fields

A response from a BridgePay gateway may contain an AuthCode from the underlying processor.

You can find this information in 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>
     <bridge_pay>
       <auth_code>2323214</auth_code>
     </bridge_pay>
  </gateway_specific_response_fields>
</transaction>