• Integration Overview
  • Consumer Payments
  • Consumer Billing
  • Healthcare
  • Disbursement Hub

Consumer Payments

  • Consumer Initiated Payments
  • Staff Initiated Payments
  • Payment Plans
  • Tokenization
  • Automatic Payment Collection
    • Automatic Payments Enrollment
    • Automatic Payments Trigger
      • Balance File Specification
      • Balance File Acknowledgement
    • Auto Payment Collect Batch Enrollment
      • Batch Unenrollment
    • Enhanced Enrollment File
    • Automatic Payments Sign Up File
  • Receipts
  • Voids
  • Refunds
  • Payment Posting
    • Polling Payment Response
    • Posting File Formats
      • EOD Posting File 1.4
      • EOD Posting File 1.3
      • EOD Posting File 1.2.2
      • EOD Posting File 1.2/1.2 CR
      • EOD Posting File 1.2.1
      • EOD Posting File 1.1/1.1 CR
      • EOD Posting File 1.1.1
      • EOD Posting File 1.0
      • EOD Posting File X12 835 1.0
      • EOD Posting File X12 835 2.0
      • EOD Posting File Lockbox A
      • EOD Posting File Lockbox A1.1
      • EOD Posting File Lockbox A v2
      • EOD Posting File Lockbox B
      • EOD Posting File Lockbox C
      • EOD Posting File Lockbox C v2
      • EOD Posting File Lockbox D
      • EOD Posting File Lockbox E
      • EOD Posting File Lockbox F
      • EOD Posting File Lockbox G
      • EOD Posting File Lockbox G v2
      • EOD Posting File LockBox H
      • EOD Posting File Lockbox I v1
      • EOD Posting File Lockbox L
      • Member Payments EOD Posting File v1.0
      • Payment Deposit File 1.0
      • Payment Deposit File 2.0
    • Webhook
    • Payment Interface Testing
    • Payment Transaction Import
      • Payment Transaction Import Data Fields
      • IDF Acknowledgement Data Fields
  • PCI Compliance
    • Recommended Options for PCI Compliance
    • Software Development Impact of PCI Compliance
    • Hosting Impact of PCI Compliance
    • P2PE Devices
  • Consumer Profile
    • Consumer Experience
    • Staff Experience
  • Digital Wallet
  • Google Pay
  • Member Payments
    • Manage Member Payment Methods
    • New Member Payment
    • View Member Payment History
    • View Member Payment Receipt
    • Member Payments Webhook
  • Member Effectuation
  • Member IDF Import v1.1
  • User Management
  • Request Sandbox API Key
  • Contact
  • Terms of Use
Skip to content
InstaMed Developer Portal
  • Integration Overview
  • Consumer Payments
  • Consumer Billing
  • Healthcare
  • Disbursement Hub
  • Consumer Initiated
    • In App Apple Pay
  • Staff Initiated
  • Payment Plans
  • Tokenization
  • Automatic Payment Collection
    • Enrollment
    • Trigger
      • Balance File Specification
      • Balance File Acknowledgement
    • Batch Enrollment
      • Batch Unenrollment
    • Enhanced Enrollment File
    • Sign Up File
  • Receipts
  • Voids
  • Refunds
  • Payment Posting
    • Polling Payment Response
    • Posting File Formats
      • EOD Posting File 1.4
      • EOD Posting File 1.3
      • EOD Posting File 1.2.2
      • EOD Posting File 1.2/1.2 CR
      • EOD Posting File 1.2.1
      • EOD Posting File 1.1/1.1 CR
      • EOD Posting File 1.1.1
      • EOD Posting File 1.0
      • EOD Posting File X12 835 1.0
      • EOD Posting File X12 835 2.0
      • EOD Posting File Lockbox A
      • EOD Posting File Lockbox A1.1
      • EOD Posting File Lockbox A v2
      • EOD Posting File Lockbox B
      • EOD Posting File Lockbox C
      • EOD Posting File Lockbox C v2
      • EOD Posting File Lockbox D
      • EOD Posting File Lockbox E
      • EOD Posting File Lockbox F
      • EOD Posting File Lockbox G
      • EOD Posting File Lockbox G v2
      • EOD Posting File LockBox H
      • EOD Posting File Lockbox I v1
      • EOD Posting File Lockbox L
      • Member Payments EOD Posting File v1.0
      • Payment Deposit File 1.0
      • Payment Deposit File 2.0
    • Webhook
    • Payment Interface Testing
    • Payment Transaction Import
      • Payment Transaction Import Data Fields
      • IDF Acknowledgement Data Fields
  • PCI Compliance
    • Recommended Options
    • Software Development Impact
    • Hosting Impact
    • P2PE Devices
  • Consumer Profile
    • Consumer Experience
    • Staff Experience
  • Digital Wallet
  • Google Pay
  • Member Payments
    • Manage Payment Methods
    • New Payment
    • View Payment History
    • View Receipt
    • Webhook
  • Member Effectuation
  • Member IDF Import v1.1
  • User Management
  • Request Sandbox API Key
  • Contact
  • Terms of Use

Staff Initiated Payments

Collect cards, cash, or checks in office (POS), by mail, online or over the phone.

  • Collect All Tender Types 
    Collect checks, cash and all card types including EMV, NFV, swipe and manual
  • Collect Anywhere (Omnichannel) 
    Collect payments in office at the POS or back office, including by phone with telephone-based keyed check support or by staff initiated mobile payments
  • Integrate Any Platform 
    Flexible integrations for native desktop and mobile/tablet apps, desktop web-based apps and consumer-facing kiosks
  • Manage Devices 
    We support a range of devices and allow configurations to be managed across accounts, workstations, users and device level profiles
  • Integrate Devices 
    Many support options including modern browsers, keyboard emulation, thin client environment support (via Citrix, Remote Desktop, VMWare, etc.), COM port and content redirection
  • Scan Checks 
    One-time or batch methods supported
  • Use Saved Cards (Tokenized) 
    If available, you can use a consumer’s saved payment method
  • Reduce Risk 
    Reduce security and compliance risks as well as PCI and PA-DSS efforts by limiting card data exposure when you use InstaMed supported P2PE encrypted devices

Integration Options

Sample testing information is available on our Payment Interface Testing page.

Single Sign-On

Standard Collect Payment 

SAML or NVP authentication is used to launch staff-facing one-time payments page and offers more robust data collection and feature set, including InstaMed receipt generation.

Review the wizard below for interface display options, code examples and implementation details.

Loading, please wait
Unable to load InstaMed example wizard. Your browser is not compatible.
Please try again using modern browser such as Google Chrome or Microsoft Edge.

Simple Collect Payment 

SAML or NVP authentication is used to launch staff-facing one-time payments page. Offers a streamlined UI that reduces the number of entry fields but limits the InstaMed UI footprint. Automatically engages the device, auto closes upon submission and suppresses receipts. .NET API can be used to launch this screen.

Review the wizard below for interface display options, code examples and implementation details.

Loading, please wait
Unable to load InstaMed example wizard. Your browser is not compatible.
Please try again using modern browser such as Google Chrome or Microsoft Edge.

REST

Recommended for new integrations where the user experience is heavily controlled by the software application. Consider pairing with the InstaMed Secure Token to manage PCI scope in an ECOM environment.

Explore our REST documentation.  If you need a Sandbox API Key, apply for one here.


NVP

HTTP POST Name Value Pair (NVP) is a simple to use format that works across all platforms.

Sample Request

POST /payment/NVP.aspx HTTP/1.1
Host: connect.instamed.com
Content-Type: application/x-www-form-urlencoded
Content-Length: 268

merchantID=1000&storeID=10&terminalID=1&userID=dynaprouser&transactionAction=AuthCapt&transactionType=CreditCard&cardPresentStatus=PresentEMV&deviceSerialNumber=98DC2522081D0A0E&deviceFirmwareVersion=30050851-D1-PCI&deviceName=DynaPro SC&encryptedEMVData=019FF982019BDFDF540A9500020000DD2E2000EBDFDF550182DFDF250898DC2522081D0A0EFA82017870820174DFDF5301005F200D42454E544F572F425249414E205F30020201DFDF4D273B343236363834303030343030393631393D31383038303030303030303030303030303030303FDFDF520105F8820126DFDF59820108A56F233FA66E53565B0A1211A6F6316AE6D5E0E3616B6804E9F659D42A5DF025C3776F338F055C66620518C29A9249B15A25E604A02415B7494759B9E602B81DA746BC77C719A7B6BA55E9A16982A1899A7316806E499D8EEFF78F0862852ECFD71B394A645FE989469D9A0C653139F8E89DDD877ED98D0609203D29FCB48442898B41030890C6741DD65BE355A6DAD7EA06DA5F8FA318CC5766C18B838BF77B054CFB6019FC52F29D38A5D6BBC2DC6C670A48CDCCA9376E1411DD7285688CC1F6C07A1BCAA2ADB0C97453DC74D42C844082B43E7575FEA994AE508BD30AD363B9EB0E5EB08BE0652EBFD75347EB43A787129C8983B31D76AFE31A91239345E5D92A66A643B652F6DFDF560A9500020000DD2E2000EBDFDF570180DFDF580101000000000000009CC45DA4&messageID=0&requestToken=true&allowPartialPayment=false&supportsMultiSignatureImageFormats=true&saveCardOnFile=false&isEMVCapableDevice=True&isEMVFallback=False

Sample Response

transactionID=3A1AB7A248524C6287FA79C6A26F7CA5&saveOnFileTransactionID=3A1AB7A248524C6287FA79C6A26F7CA5&emvResponse=002DF9820029DFDF540A9500020000DD2E2000EBDFDF550182DFDF250898DC2522081D0A0EFA82000670048A02303000F3BF7984

SOAP

SOAP Web Services utilizing SOAP version 1.1 or SOAP version 1.2 to transport data. Connectivity requires 2048 bit TLS security.

DoCreditCardAuthAndCapt

https://connect.instamed.com/payment/service.asmx?op=DoCreditCardAuthAndCapt

DoECheckAuthAndCapt

https://connect.instamed.com/payment/service.asmx?op=DoECheckAuthAndCapt

.NET API

For Windows-based applications to outsource device support including EMV/NFC. Works in local and thin client environments.

Learn more


InstaMed Online

Software vendors who do not yet have a consumer-facing application to embed into can leverage this standalone portal.


Device Support

Device support is managed by InstaMed if .NET API or SSO is used. Clients can use the InstaMed Device Service for modern browser support and certain device models. For a list of P2PE devices supported and available through InstaMed, please see here.

Build a better healthcare payments experience with InstaMed

Talk With an InstaMed Expert
  • Request Sandbox API Key
  • Contact
  • Terms of Use

InstaMed is a wholly owned subsidiary and is a registered MSP/ISO of JPMorgan Chase Bank, N.A. Additionally, InstaMed is a registered ISO of Wells Fargo Bank, N.A., Concord, CA; a registered ISO of U.S. Bank, N.A.; and a registered MSP/ISO of Elavon, Inc. Georgia.

  • Twitter
  • LinkedIn
  • YouTube

© 2023 JPMorgan Chase & Co. All rights reserved.Privacy StatementTerms of Use