CT Site Admin Integration

Instant Issue – Non-Personalized

  • Step 1: CT Site order bulk inventory to hold on-site for allocation to new Patients.
  • Step 2: Patient is onboarded within the site CTMS System.
  • Step 3: CT Site will provide the required Patient data to Dash along with the Proxy from the inventory held on-site to register a card to the Patient.
  • Step 4: Dash will create the card account and return the proxy for confirmation. Patients can activate their card by following the instructions in the carrier or through the IVR with the number on the back of the card.
  • Step 5a: The Sponsor will either fund the site or the master virtual funding account directly.
  • Step 5b: Virtual Funding Account will be prefunded by the Site/Sponsor prior to loadings cards.
  • Step 6: The Patient completes a treatment and is eligible for funding, so the site triggers a load to the card using the proxy.
  • Step 7: The card account is funded with the appropriate amount per the load instructions.

WALKTHROUGH

Step 1: Get Shipping Methods

Description:

This step will provide the available carrier and delivery speed methods available.

Pre-requisites:

sessionId – Acquired during the authentication process

Endpoint Details:

  • API Endpoint – /customerendpoint/v1
  • Call Type – GET
  • Path – /getShippingMethods

Considerations:

Response will return a list of current carrier and delivery speed identifiers to be used Step 2

Code Snippet:

Required Parameters

"sessionId": "uywbzibgbfgaienonrgyxahwuwegrtpssvvljdpypfkotqdjqsbydd10906"

Step 2: Order Bulk Inventory

Description:

This step will execute the creation of the bulk inventory for physical cards to be delivered to a specified location.

Pre-requisites:

  • sessionId – Acquired during the authentication process
  • customerId – provided during client setup. Can be accessed from the /getCustomerList endpoint
  • custProgId – provided during program setup. Can be accessed from the /getCustomerProgramList endpoint

Endpoint Details:

  • API Endpoint – /orderendpoint/v1
  • Call Type – POST
  • Path – /orderCards

Considerations:

Response will return the orderId as the unique identifier for the order for reporting purposes

Code Snippet:

Required Parameters

"sessionId": "uywbzibgbfgaienonrgyxahwuwegrtpssvvljdpypfkotqdjqsbydd10906"
{
"custProgId": "{{cpIdIIC}}",
"customerId": "{{customerId}}",
"qty": 1,
"shippingMethod": "USPS First Class",…

Step 3: Inventory Status & Tracking

Description:

This step will provide a list of orders, status or orders, and tracking information (if applicable) based on defined criteria.

Pre-requisites:

  • sessionId – Acquired during the authentication process
  • customerId – Provided during client setup
  • startDate / endDate – Used to isolate orders for a specific time frame.

Endpoint Details:

  • API Endpoint – /customerendpoint/v1
  • Call Type – POST
  • Path – /getInventoryDetails

Considerations:

Response will return a list of orders based on the criteria provide in the payload
Order status and tracking information can be accessed here to follow inventory delivery

Code Snippet:

Required Parameters

"sessionId": "uywbzibgbfgaienonrgyxahwuwegrtpssvvljdpypfkotqdjqsbydd10906"
{
"customerId": 98709,
"startDate": "2025-01-23",
"endDate": "2025-02-08",
"orderStatus": [Ordered, Shipped, Failed],…

Step 4: Register

Description:

This step will assign a card in the onsite inventory to a specific Patient.

Pre-requisites:

  • sessionId – Acquired during the authentication process
  • proxyKey – Provided on the physical inventory
  • custProgramId – provided during program setup. Can be accessed from the /getCustomerProgramList endpoint
  • customerId – provided during program setup

Endpoint Details:

  • API Endpoint – /fisendpoint/v1
  • Call Type – POST
  • Path – /registerCards

Considerations:

  • Response will return a list of card elements including the detailOrderId
  • The ProxyKey and/or routing/account numbers should be stored at this stage for loading the card based on the specific CT Site’s funding flow.

Code Snippet:

Required Parameters

"sessionId": "uywbzibgbfgaienonrgyxahwuwegrtpssvvljdpypfkotqdjqsbydd10906"
{
"custProgId": "{{cpIdIIC}}",
"customerId": "{{customerId}}",
"orderDetails": [
{
"proxyKey": "string",
"email": "[email protected]",
"phone": "string",
"firstName": "string",
"lastName": "string",…

Step 5: Replace

Description:

This step will be used if an Patient already has a registered card that is lost or damaged, and will issue them a new physical card from the inventory while keeping all of the underlying account data / balances the same.

Pre-requisites:

  • sessionId – Acquired during the authentication process
  • proxyKey – Acquired during the original order request
  • cpId – provided during program setup. Can be accessed from the /getCustomerProgramList endpoint

Endpoint Details:

  • API Endpoint – /fisendpoint/v1
  • Call Type – POST
  • Path – /replaceCard

Considerations:

  • Response will return the same card details for the new card in line with what was returned during the register step.
  • The proxy and routing/account number that was stored during the registration of the original card will be maintained for future loads.

Code Snippet:

Required Parameters

"sessionId": "uywbzibgbfgaienonrgyxahwuwegrtpssvvljdpypfkotqdjqsbydd10906",
{
"cpId": "{{cpIdIIC}}",
"proxyKey": "string",
"newProxyKey": "string"
}