Setup

Request Development Account

Send an email to integrations@runpayments.io including your name, email, and company. You will be assigned an Integration Delivery lead who will set you up with the following:

  • UAT Merchant ID
  • Payment API Credentials including an api_key, refresh_token, and public_key delivered via a secure link.
  • Run Merchant User Account for viewing transactions during development and testing.

Generate API credentials

Once you have logged into your Run Merchant account, you can also use the Settings page to generate Payments and Reporting API credentials on your own.

Generating new Reporting API credentials will invalidate any existing Reporting API credentials you have and issue a new client id and secret.

Postman Collection

The Postman Collection for the Payments and Reporting APIs can be found at the link below:

Once you have forked or imported the collection, navigate to the Environments tab to enter your API key and ensure you have the correct environment variables set:

VariableTypeInitial Value
pay_urldefaulthttps://javelin.runpayments.io/
middefaultEnter the MID provided by your Integration Delivery lead.
api_keysecretEnter the api_key provided by your Integration Delivery lead.
refresh_tokensecretEnter the refresh_token provided by your Integration Delivery lead.
reporting_urldefaulthttps://apps.runpayments.io/ords/sprint
reporting_client_iddefaultEnter the client ID generated from the Run Merchant Settings.
reporting_secretsecretEnter the secret generated from the Run Merchant Settings.

Test Cards

To generate a payment account token for running transactions, you may either implement the Runner.js service or use the tokenizer in the Developer section of your Run Merchant portal. In your UAT environment, data is never sent to the end processor. The below test cards may be used for transactions in your UAT environment:

Card TypeCard Number
Visa4788250000121443
Mastercard5454545454545454
AMEX371449635398431
Discover6011000995500000