Gateway Configuration

This page details the configuration object for various gateways supported by Platform

Authorize.net

"configuration": {
    "name": "<authorize.net provided name>",
    "transaction_key": "<authorize.net transaction key>"
}

Platform's OAuth implementation for Authorize.Net can also be utilized to configure Authorize.Net without directly transmitting the transactionKey.

This technical overview presents a method for integrating Authorize.Net that circumvents the direct transmission of the transactionKey. The approach employs Platform's OAuth implementation, explicitly designed to facilitate secure and efficient integration with the Authorize.Net platform.

Using Platform Webcomponent

<!-- Platform Web Component -->
<payment-platform 
  type="gateway-connect" 
  gateway-id="authorize.net"
  merchant-id="<YOUR Merchant ID>">
</payment-platform>

<pre id="result"></pre>
<!-- Handling Event from component -->
<script>
  const el = document.querySelector('payment-platform')
  const output = document.getElementById('result')
  el.addEventListener('success', function(event) {
    console.log('success', { event })
    output.innerHTML = JSON.stringify(event.detail, null, 4)
  })
  el.addEventListener('failure', function(event) {
    console.log('failure', { event })
    output.innerHTML = JSON.stringify(event.detail, null, 4)
  })
</script>

Using Javascript to create your own UI

Stripe

stripeAccount is only required for Stripe Connect

Elavon

NMI

Using Security Key

Using Username and Password

TSYS

EVO

Global Payments East - EMV

World Pay

Last updated