Employer Admin Integration

Personalized –Digital First + Physical

  • Step 1: Employee is onboarded within the client HRIS / Payroll / PEO System.
  • Step 2: Client will provide the required Employee data to Dash to issue a card to the Employee.
  • Step 3: Dash will create the card account with the Sponsor Bank/Processor and return the PANProxy & DDA Account details for that Employee.
  • Step 4: The Employee will receive an email and/or sms message allowing them to activate their card account for immediate access. A physical card will simultaneously be sent to the Employee.
  • Step 5: Client will send due funds to the Employee using either the stored PANProxy or the DDA Account details.
  • Step 6: The Employee card account is funded and available for use.

WALKTHROUGH

Step 1: Order / Issue Cards

Description:

This step will execute the creation of the card account and issue the card to the employee

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:

  • Card Type designation of digital will be used to provide immediate access to the card account.
    • Client configuration options would allow for issuing a digital card with a physical being automatically sent or physical cards can be requested by the cardholder in the digital experience.
    • Physical first personalized cards would designate the card type as ‘physical’.
  • Response will return 4 key identifiers that need to be stored by on the client side:
    • orderId – This is a unique identifier for the order that will be used to physical card tracking
    • proxyKey – This is an overall unique account identifier that is used for reference or ancillary API calls. This is also used in loan/unload calls for specific scenarios
    • trn/dda – These two fields are the aba routing and account numbers for the virtual account that are used for loading funds.
    • personId – This is used when updating employee profile data

Code Snippet:

Required Parameters

"sessionId": "uywbzibgbfgaienonrgyxahwuwegrtpssvvljdpypfkotqdjqsbydd10906"
{
"custProgId": 987654,
"customerId": 12345,
"orderProdType": "Personalized Payroll Order",
"cardType": "Digital",
"orderDetails": [
{
"firstName": "string",
"lastName": "string",
"phone": "string",
"email": "string", …

Step 3: Resend Digital Card Account Links

Description:

This step will trigger a resend of the email or sms notification to the Empoyee to activate and/or access the card feature through the digital experience.

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 – /orderendpoint/v1
  • Call Type – GET
  • Path – /sendDigitalCardAlert

Considerations:

  • Response will return a success or failure
  • Separate calls are needed between email or sms notification triggers

Code Snippet:

Required Parameters

"sessionId": "uywbzibgbfgaienonrgyxahwuwegrtpssvvljdpypfkotqdjqsbydd10906"
{
"cpId": 987654,
"proxyKey": 9376873800385,
"resendMethod": "[email] or [sms]",
"alertType": "Initial"
}…

Step 3: Order Details

Description:

This step will recall the complete order information

Pre-requisites:

  • sessionId – Acquired during the authentication process
  • orderId – Acquired during the order step

Endpoint Details:

  • API Endpoint – /orderendpoint/v1
  • Call Type – GET
  • Path – /getOrderDetailsByOrderId

Code Snippet:

Required Parameters

"sessionId": "uywbzibgbfgaienonrgyxahwuwegrtpssvvljdpypfkotqdjqsbydd10906",
"proxyKey": "1234567890123",
"customerProgramId": ”987654"

Step 4: Shipping Details [OPTIONAL]

Description:

This step will recall the shipping information for the physical card delivery and provide tracking if available

Pre-requisites:

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

Endpoint Details:

  • API Endpoint – /orderendpoint/v1
  • Call Type – GET
  • Path – /getShippingInformation

Considerations:

For bulk or batch order, the /getOrderTrackingInfo endpoint should be used.
Shipping webhooks are available for pushing updates to client systems to reduce the resources required for pulling tracking on set schedules.

Code Snippet:

Required Parameters

"sessionId": "uywbzibgbfgaienonrgyxahwuwegrtpssvvljdpypfkotqdjqsbydd10906",
"proxyKey": "1234567890123",
"customerProgramId": ”987654"