Windcave (formerly Payment Express) Gateway Guide
close
Services and Compatibility
- Payment Gateway Company Name:
- Windcave (formerly Payment Express)
- Services that work with Spreedly:
-
- Merchant Hosted Payment Express Gateway
- Services that do not work with Spreedly:
-
- DPS Hosted Payment Express Gateway
- Supported operations:
- Purchase, Authorize, Capture, Refund, Verify, Store
- Unsupported operations:
- Void
- Supported payment types:
- Credit Card
- Spreedly 3DS2 Global Supported
- No
- Gateway Specific 3DS1 Supported
- No
- Gateway Specific 3D2 Supported
- No
- Regions:
- Asia Pacific, Europe, North America
- API endpoint URL:
-
https://sec.paymentexpress.com/pxpost.aspx
Authentication and Security
- Specific names for credentials:
- Login, Password
Onboarding Merchants in:
Additional Notes
Spreedly integrates with Windcave’s PxPost platform only. PxPost uses the terms username
and password
for its credentials. Creating a Spreedly gateway with PxPay or PxFusion credentials will result in authentication errors.
Adding a Windcave (formerly Payment Express) gateway
To add a Windcave (formerly Payment Express) gateway:
curl https://core.spreedly.com/v1/gateways.xml \
-u 'C7cRfNJGODKh4Iu5Ox3PToKjniY:4UIuWybmdythfNGPqAqyQnYha6s451ri0fYAo4p3drZUi7q2Jf4b7HKg8etDtoKJ' \
-H 'Content-Type: application/xml' \
-d '<gateway>
<gateway_type>payment_express</gateway_type>
<login>login</login>
<password>password</password>
</gateway>'
<gateway>
<token>Ln91mcagCZDrNZ3Tn2c9ZUoiyFR</token>
<gateway_type>payment_express</gateway_type>
<name>Payment Express</name>
<description nil="true"/>
<login>login</login>
<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">false</supports_void>
<supports_verify type="boolean">false</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>login</name>
<value>login</value>
</credential>
</credentials>
<gateway_specific_fields>
<gateway_specific_field>txn_data1</gateway_specific_field>
<gateway_specific_field>txn_data2</gateway_specific_field>
<gateway_specific_field>txn_data3</gateway_specific_field>
</gateway_specific_fields>
<payment_methods>
<payment_method>credit_card</payment_method>
<payment_method>third_party_token</payment_method>
</payment_methods>
<state>retained</state>
<redacted type="boolean">false</redacted>
<created_at type="dateTime">2018-06-19T17:08:00Z</created_at>
<updated_at type="dateTime">2018-06-19T17:08:00Z</updated_at>
</gateway>
env = Spreedly::Environment.new('C7cRfNJGODKh4Iu5Ox3PToKjniY', '4UIuWybmdythfNGPqAqyQnYha6s451ri0fYAo4p3drZUi7q2Jf4b7HKg8etDtoKJ', base_url: 'https://core.spreedly.com')
env.add_gateway(:payment_express, login: "Your login", password: "Your password")
#<Spreedly::Gateway:0x007fe333b26830
@token="2uiRxqJQoT2WVyNQboSeac84Pdm",
@created_at="2017-07-27T17:49:58Z",
@updated_at="2017-07-27T17:49:58Z",
@gateway_type="payment_express",
@state="retained",
@name="Payment Express",
@credentials={"login"=>"Your login"}>
Gateway specific fields
When interacting with Windcave (formerly Payment Express) gateway to run transactions, there are gateway specific fields you can specify.
txn_data1
txn_data2
txn_data3
These don’t impact any gateway operations; rather, they’re simply stored by the gateway alongside the transaction for your use.
Gateway specific response fields
A response from the gateway may contain the following gateway specific response field:
<transaction>
<token>LgpTNGjsWQs9DwdxcbreUVz0R8p</token>
<transaction_type>Purchase</transaction_type>
<gateway_specific_response_fields>
<payment_express>
<auth_code>123456</auth_code>
</payment_express>
</gateway_specific_response_fields>
</transaction>