• 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

Refunds

Integrate refund (or credit) transactions to transfer funds to a consumer account

Types

  • Simple Refund: a refund tied to a specific transaction and can only be made to an amount less than or equal to the original transaction amount. It can be performed up to three months following a transaction using the original transaction ID.
  • Standalone Refund: a refund sent directly to a consumer account using payment details via a card swipe or manual key. Standalone refund transactions are not available via EMV or NFC payment methods.

Integration Options

Refunds may be implemented differently than payment transactions.

Refund Payment SSO

Refunds may be integrated via Single Sign-On (SSO) for provider facing implementations. The receipt is generated by InstaMed.

Review the wizard below for interface display options, code examples and integration 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. 

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: NNN

transactionType=CreditCard&transactionAction=SimpleRefund&MerchantID=123123123&StoreID=123&TerminalID=123&primaryTransactionID=2FA23B1C2C8C4E0D951C24EB300DCCFB&primaryCardPresentStatus=PresentManualKey&amount=10.00&

Sample Response

IsEMVVerifiedByPIN=false&isEMVTransaction=FALSE&EMVCardEntryMode=KEYED&cardBrand=DISCOVER&cardExpirationMonth=12&cardExpirationYear=2019&cardBINNumber=601100&cardHolderName=JOE MONTANA&paymentCardType=CREDIT&lastFourDigits=9424&authorizationNumber=9A5DDA&responseCode=000&responseMessage=APPROVAL&transactionStatus=C&primaryTransactionID=D5E2BF0800AB41CEAC2D8CBF406E800E&authorizationText=THE ABOVE AMOUNT HAS BEEN REFUNDED.&transactionID=96A66FDA25964C8F9C0AEB0EF8123AAF&transactionDate=2016-04-27T19:17:05.2770143Z&saveOnFileTransactionID=2FA23B1C2C8C4E0D951C24EB300DCCFB

SOAP

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

DoCreditCardSimpleRefund

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

DoCreditCardCredit

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

DoECheckCredit

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

InstaMed Online

Standalone portal for software vendors who do not yet have a consumer-facing application to embed into.

https://online.instamed.com/providers/Form/PatientPayments/NewPatientPayment

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 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