• 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

Consumer Initiated Payments

Accept cards and eChecks on web apps, mobile apps or IVR

  • Convenient Payment Methods 
    eCheck, card and Apple Pay
  • Integrate Any Platform 
    Native desktop and mobile/tablet apps, web-based apps and consumer-facing kiosks
  • Save Payment Methods (Tokenize) 
    Payment methods can be saved and managed in a digital wallet

Integration Options

Use any of the following to minimize development costs and compliance (PCI and PA-DSS) efforts:

  • Embed InstaMed’s UI using Single Sign-On
  • Use web service protocols (e.g. REST, NVP, or SOAP)
  • Use the InstaMed Secure Token
  • Link directly to InstaMed Online.

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

Single Sign-On 

Create and build a consistent consumer experience over multiple visits using SAML or NVP authentication via Single Sign-On. Add advanced features such as digital wallet, self-service payment plans, eStatement authentication, text messaging enrollment and the ability to view balances.

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.

InstaMed Secure Token

Reduce the PCI scope for consumer-facing applications by allowing InstaMed to tokenize the payment instrument. Applications can maintain their preexisting web services payment interfaces and control the rest of the user experience. This approach is best used with REST, NVP or SOAP technologies.

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

Recommended for integration across all platforms, HTTP POST Name Value Pair (NVP) is a simple to use format.

Sample Request

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

cardPresentStatus=NotPresentInternet&transactionType=CreditCard&transactionAction=AuthCapt&MerchantID=123123123&StoreID=123&TerminalID=123&cardNumber=4111111111111111&cardHolderName=Aaron Smith&cardExpDate=12-19&amount=5.00&cardVerificationNumber=123&billingAddress1=123 Main  Apt 23&billingCity=Madison&billingState=WI&billingZip=53703&

Sample Response

IsEMVVerifiedByPIN=false&cardBrand=VISA&cardExpirationMonth=12&cardExpirationYear=2019&cardBINNumber=411111&cardHolderName=AARON SMITH&paymentCardType=CREDIT&lastFourDigits=1111&authorizationNumber=9A5C83&responseCode=000&responseMessage=APPROVAL&transactionStatus=C&authorizationText=I AGREE TO PAY THE ABOVE AMOUNT ACCORDING TO MY CARD HOLDER AGREEMENT.&transactionID=E8936AED682E4EC38FCBD2BE52CA82F6&transactionDate=2016-04-06T19:21:33.1493632Z

SOAP

Recommended when the required 2048 bit TLS security is available, SOAP Web Services (versions 1.1 or 1.2) can be used to transport data.

DoCreditCardAuthAndCapt

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

DoECheckAuthAndCapt

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

In App Apple Pay SDK

Recommended integration protocol when embedding within iOS native apps.

Learn more


InstaMed Consumer Portal

This standalone portal can be easily leveraged for consumer interactions where there is no current consumer-facing application.

pay.instamed.com

Embed Consumer One-Time Payment

Users can make a one-time payment and have the necessary metadata passed into the application. A balance can be displayed after the transaction if the optional one-time authentication is enabled.

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.

Next Steps

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