FlexShopper API
3.0-legacy
FlexShopper API
3.0-legacy
  • Getting Started
  • Our Platforms
    • FlexPay Payment Platform
    • FlexShopper Backend API
  • API Reference
    • Get Started
      • API Requests
      • API Responses
      • Error Codes
    • User Management
      • Create User
      • Get Users
      • Get User
      • Verify User Exists
      • Deeply Verify User Exists
      • Get LoanPaymentPro Child Key
      • Add Payment Method
    • Customer Authentication
      • Request Passcode
      • Login Customer
    • Customer Application
      • Initiate Application
      • Get Verification Questions
      • Verify Answers
      • Validate Routing Number
    • Lease Management
      • Create Lease
      • Get Lease By ID
      • Sign Lease
      • Checkout
    • Purchase Transactions
      • Get Transactions
      • Get Transaction By ID
      • Cancel Items
      • Return Items
      • Confirm Shipment
      • Confirm Receipt
    • Products
      • Get Products
    • Settings
  • Change Log
Powered by GitBook
On this page
  • Customer Login
  • Customer Application
  • Purchase Transactions

Was this helpful?

Export as PDF
  1. Our Platforms

FlexShopper Backend API

FlexShopper Backed gives external marketplace full integration through our public API. Using our API integrators can implement their own solutions to provide a seamless experience to theirs customers.

PreviousFlexPay Payment PlatformNextAPI Reference

Last updated 10 months ago

Was this helpful?

Customer Login

Customers will need to be able to request a temporary passcode from FlexShopper via SMS or email. This passcode, along with their email address, will be used to login to the system.

The passcodes FlexShopper sends to users are temporary, single-use, and only valid for a few minutes. They should not be cached, batched, logged, or stored in any other way; they should be sent immediately.

The Customer Tokens used for authenticating with the system are associated with the API key used to generate them, and they should only be used in conjunction with that particular API key. If a request with a Customer Token is received with a *different* API key than the one used to generate it, both accounts may be suspended.

Find below endpoints needed to authenticate a customer

Customer Application

To complete a successful customer application the integrator must follow the proper flow and use the right endpoints.

Find below endpoint to complete a customer application

After a customer successful application it might need to verify the identity, find below the necessary endpoints to complete

Purchase Transactions

A purchase transaction starts creating a Lease and then signing it. When the vendor ship the order, this one should be acknowledged using confirm-shipment endpoint.

Find below endpoints needed to complete a customer transaction

Request Passcode
Login Customer
Get User
Request Passcode
Initiate Application
Get Verification Questions
Verify Answers
Create Lease
Get Lease By ID
Sign Lease
Confirm Shipment
Confirm Receipt