RESTful Transaction API
The REST interface Developer Documentation: Transaction API Development Guide
REST Interface
The BridgePay Transaction API is a RESTful API for interfacing with the BridgePay Gateway. The API includes familiar transaction types from the BridgeComm API in a user friendly JSON interface.
BridgePay’s Transaction API can be used to process both Card Present and Card Not Present transactions. A card present transaction is defined as a transaction in which the card data was directly read from a credit or debit card. This includes EMV and track data transactions. A card not present transaction is defined as a transaction in which card data is manually keyed, such as a mail-order/telephone-order or Ecommerce transaction.
NOTE: As a prerequisite to use the Transaction API for card present transactions, an integrator must perform a direct integration to their intended card reader in order to read and obtain the card data and format it into a Transaction API request. A direct integration may be performed to devices BridgePay has certified with our processors. Please view the certified devices list for clarity.
If an integrator intends to perform a direct to device integration, please connect with the BridgePay Integration team to discuss best practices and for guidance connecting with device providers.
Looking to find what transaction types the RESTful Transaction API supports?
Have a look at our BridgePay Product Matrix
Property of BridgePay Network Solution ©2024