Skip to main content
A point-of-sale (POS) integration lets borrowers complete required verification steps without leaving the loan application flow. Point of sale systems integrate with Argyle.

​
Choose an integration model

​
Verifications

Use the Verifications API when the POS creates and tracks standardized payroll, banking, or Doc VOI orders.
  1. Create or reuse the borrower as an Argyle user.
  2. Order the required verification products.
  3. Create a session for payroll or banking user action.
  4. Launch the connection flow from the POS.
  5. Wait for the verifications.updated webhook and retrieve the completed reports.
This model gives each requested product its own verification status and report result.

​
Direct Data APIs

Use the Data APIs when the POS already has a custom workflow that consumes connected-account data directly.
  1. Create the user and a user token.
  2. Embed Link in the application.
  3. Track each connected account independently.
  4. Wait for the required account and resource events.
  5. Retrieve the data sets used by the application.

​
Launch the user experience

​
Payroll

  • Embed the Web SDK or a supported Mobile SDK.
  • Use a verification session link as connectUrl, or initialize a direct-data flow with userToken.
  • Use Link callbacks to update the immediate POS experience.

​
Banking

  • Create a verification session and pass its link to the banking SDK as connectURL.
  • Use banking SDK callbacks for immediate frontend handling.
  • Use the verifications.updated webhook for backend status.

​
Doc VOI

  • Collect documents in the POS and upload them through the User Uploads API, or direct the borrower to the configured document-upload experience.
  • Track document processing through the verification lifecycle.

​
Return to the application

Set a session redirect_url or handle the relevant SDK callback after the borrower finishes the current step. Treat the backend verification or account webhook as the source of truth for processing status.

​
Reports and data

  • Verification implementations retrieve completed reports from the verification resource.
  • Direct-data implementations retrieve users, accounts, identities, paystubs, payroll documents, and other required data sets from the API.
  • Source files and report URLs require Argyle authentication headers.

​
Supported integrations

For supported prebuilt POS integrations, see: For another platform, use this page as the implementation model and confirm platform-specific requirements with your Argyle Customer Success Manager.