Boarding API (v1.0.5)
Download OpenAPI specification:Download
Welcome to the Boarding API documentation!
Here you will find our collection of endpoints for boarding an managing accounts.
This is the reference documentation and schemas for the Boarding API.
The platform uses API Keys to manage access to the API. You can pass the API key in the x-api-key header to the request.
Talk you your sales rep about acquiring these API keys.
Authorization is done via headers. You should pass the api key as the value to the x-api-key header. For example, x-api-key: ${API_KEY}.
Please note that you will be given 2 API keys, one public key and one private key. Use the private key for all server to server communication. The public key is used for interfacing wih the JS SDK.
A Forward Account is created when you have an Application that has gone through the boarding process to get to an approved state. You can update your Account, fetch a particular Account as well as find all the Accounts that you are associated with. If there was something incorrect for your Account you can also update details for an Account. Note:
- Each Account is required to have a Company as well as an Address.
- You can only view and modify Accounts if you have the correct level of access.
Patch an Account
Partial updates to Account are allowed as needed. This will fully replace user_fields if provided.
Authorizations:
path Parameters
| id required | string |
Request Body schema: application/json
| name required | string [ 0 .. 100 ] characters Account name |
| recruited_by | string Account Recruited By User Name/Email |
required | object (AccountCompanyUpdateDto) Company Information |
| location_id | string [ 0 .. 100 ] characters Account Location Id |
required | object (AddressDto) Address Info |
object User-defined fields as free-form JSON object |
Responses
Request samples
- Payload
{- "name": "string",
- "recruited_by": "string",
- "company": {
- "ownership_type": "GOVERNMENT",
- "category": "RETAIL",
- "ein": "string",
- "legal_name": "string",
- "dba_name": "string",
- "description": "string",
- "business_start_date": "2019-08-24",
- "website": "string",
- "timezone": "EST",
- "phone_number": "8005550100",
- "mcc": "string"
}, - "location_id": "string",
- "address": {
- "country": "US",
- "state": "AL",
- "city": "string",
- "zip_code": "35242",
- "address_line1": "string",
- "address_line2": "string"
}, - "user_fields": {
- "property1": { },
- "property2": { }
}
}This is an object that represents a Forward Application. This is how you get started on Forward to initiate the process of having an Account. You can Create a Draft Application or Update the Draft Application. Additionally, you can also generate an Application Link to update or submit a new Boarding application. All the Applications that were created by you can also be retrieved.
Fetch a boarding Application by id
Retrieve complete details about a specific boarding application by its unique identifier. This endpoint returns all application information including status, business details, company information, and configuration. Use this to review application details at any stage of the onboarding process, from draft to approved status.
Authorizations:
path Parameters
| id required | string |
Responses
Update an existing draft boarding Application
Update an existing draft boarding application to modify or complete application details. Important: This endpoint can only be used to update applications that are in DRAFT status. Once an application has been submitted and moved to other statuses (such as UNDER_REVIEW, APPROVED, etc.), it cannot be updated through this route. Use this to save your progress, correct information, or add missing details before submitting the application.
Authorizations:
path Parameters
| id required | string |
Request Body schema: application/json
| business_id required | string The Business ID |
| name required | string [ 0 .. 100 ] characters Account Name |
| sales_code_id | string [ 0 .. 50 ] characters Sales Code ID |
object (AccountCompanyRequestDto) Company Information - Supports both US (EIN) and Canadian (BN) applications | |
object (AddressRequestDto) Address Info | |
object (IndustryVolumeRequestDto) Industry & Volume Information | |
| ach_volume | integer <int32> Application Ach Volume Info |
object (ServicesDeliveriesRequestDto) Service Delivery Information | |
object (TransactionModesRequestDto) Service Delivery Information | |
Array of objects (OwnerUpdateRequestDto) Owners Information | |
| processing_plan_id | string Processing Plan id |
| terms_accepted | boolean Terms and Conditions are accepted or not |
object (PartnerDataDto) Partner Data Information | |
| country | string [ 0 .. 10 ] characters ^(US|CA)$ Default: "US" Country code - US or CA |
object User-defined fields as free-form JSON object |
Responses
Request samples
- Payload
{- "business_id": "string",
- "name": "string",
- "sales_code_id": "string",
- "company": {
- "ownership_type": "GOVERNMENT",
- "category": "RETAIL",
- "ein": "string",
- "legal_name": "string",
- "dba_name": "string",
- "description": "string",
- "business_start_date": "2019-08-24",
- "website": "string",
- "timezone": "EST",
- "phone_number": "8005550100",
- "mcc": "7021",
- "stock_symbol": "string"
}, - "business_address": {
- "country": "US",
- "state": "AL",
- "city": "string",
- "zip_code": "35242",
- "address_line1": "string",
- "address_line2": "string"
}, - "industry_volume": {
- "avg_annual_volume": 999999999,
- "avg_ach_annual_volume": 999999999,
- "avg_ticket_amount": 99999,
- "high_ticket_amount": 0,
- "avg_ach_ticket_amount": 0,
- "ach_high_ticket_amount": 0
}, - "ach_volume": 0,
- "services_deliveries": {
- "same_day_delivery": 0,
- "one_week_delivery": 0,
- "two_week_delivery": 0,
- "one_month_delivery": 0,
- "more_than_one_month_delivery": 0
}, - "transaction_modes": {
- "in_person": 0,
- "online": 0
}, - "owners": [
- {
- "id": "string",
- "first_name": "string",
- "last_name": "string",
- "email": "string",
- "phone_number": "string",
- "title": "OWNER",
- "ownership_percent": 0,
- "ssn": "string",
- "birth_date": "2019-08-24",
- "residence_address": {
- "country": "US",
- "state": "AL",
- "city": "string",
- "zip_code": "35242",
- "address_line1": "string",
- "address_line2": "string"
}, - "signer": true
}
], - "processing_plan_id": "string",
- "terms_accepted": true,
- "partner_data": {
- "paid_subscription": true,
- "merchant_joined": "2019-08-24T14:15:22Z",
- "backbook": true,
- "last_ip_address": "string",
- "sub_payor_name": "string",
- "request_credit_override": true,
- "prior_annual_volume": 999999999,
- "prior_avg_ticket": 999999999,
- "prior_high_ticket": 999999999,
- "six_mos_chargeback_rate": 0,
- "six_mos_refund_rate": 0,
- "redirect_url": "string"
}, - "country": "US",
- "user_fields": {
- "property1": { },
- "property2": { }
}
}Deleting an existing Application in DRAFT or CANCELLED state
Permanently delete a boarding application that is in DRAFT or CANCELLED status. Important: This operation can only be performed on applications in DRAFT or CANCELLED states. Applications in other statuses (such as UNDER_REVIEW, APPROVED, DECLINED, etc.) cannot be deleted. Once an application is deleted, it will be permanently removed and will no longer appear in application lists or be accessible through the API. Use this to clean up draft applications that are no longer needed or to remove cancelled applications from your records.
Authorizations:
path Parameters
| id required | string |
Responses
List boarding Applications
Retrieve a paginated list of all boarding applications associated with your account. Use the request parameters to filter results by status, business ID, or creation timestamps. This endpoint is useful for monitoring all your applications across different stages of the onboarding process, from draft applications to those under review, approved, or declined.
Authorizations:
query Parameters
required | object (ApplicationFilterRequestDto) Application Filter Request |
Responses
Create a boarding Application
Create a new draft boarding application to initiate the onboarding process on Forward. This endpoint creates an application in DRAFT status, which allows you to save your progress and complete the application over time. Note: Most fields in the request are optional - you can create a minimal draft and add details later, or provide complete information upfront.
Important: Once the application is submitted (via application link), it will be processed and go through our approval workflow. Note: Webhooks are available to receive real-time notifications about application status changes, eliminating the need for polling.
Country: The country field (or address.country) determines US vs Canadian (CA) application behavior. Set country to US or CA accordingly; ownership types and validations depend on the selected country.
Company Ownership Types and Owner Titles (US): The following mapping shows valid owner titles for each company ownership type. Note: These are optional during the 'Create Application' step and can be provided later.
LIMITED LIABILITY COMPANY
- PRESIDENT
- VICE_PRESIDENT
- TREASURER
- CEO
- CFO
- COO
- SECRETARY
- MEMBER
PRIVATE
- PRESIDENT
- VICE_PRESIDENT
- SECRETARY
- TREASURER
- CEO
- CFO
- COO
TAX EXEMPT ORGANIZATION
- ADMINISTRATOR
SOLO TRADER
- OWNER
PARTNERSHIP
- PARTNER
GOVERNMENT
- ADMINISTRATOR
PUBLIC
- ADMINISTRATOR
Canadian (CA) Business Types and Owner Titles: For applications with country = CA, use one of the following ownership types and the corresponding owner titles.
SOLE_PROPRIETORSHIP
- OWNER
GENERAL_PARTNERSHIP
- PARTNER
LIMITED_PARTNERSHIP
- PARTNER
PRIVATE_CORPORATION_FEDERALLY_OR_PROVINCIALLY_INCORPORATED
- PRESIDENT
- VICE_PRESIDENT
- SECRETARY
- TREASURER
- CEO
- CFO
- COO
PUBLIC_CORPORATION_SHARES_TRADED_ON_EXCHANGE
- PRESIDENT
- VICE_PRESIDENT
- SECRETARY
- TREASURER
- CEO
- CFO
- COO
COOPERATIVE_FOR_PROFIT
- PRESIDENT
- VICE_PRESIDENT
- SECRETARY
- TREASURER
- CEO
- CFO
- COO
COOPERATIVE_NOT_FOR_PROFIT
- OWNER
- PARTNER
- PRESIDENT
- VICE_PRESIDENT
- SECRETARY
- TREASURER
- CEO
- CFO
- COO
- MEMBER
NOT_FOR_PROFIT_ORGANIZATION_NON_CHARITY
- OWNER
- PARTNER
- PRESIDENT
- VICE_PRESIDENT
- SECRETARY
- TREASURER
- CEO
- CFO
- COO
- MEMBER
REGISTERED_CHARITY
- OWNER
- PARTNER
- PRESIDENT
- VICE_PRESIDENT
- SECRETARY
- TREASURER
- CEO
- CFO
- COO
- MEMBER
GOVERNMENT_ENTITY_FEDERAL_PROVINCIAL_MUNICIPAL_CROWN_CORPORATION
- No owner titles required (government entity)
UNLIMITED_LIABILITY_CORPORATION_ULC
- PRESIDENT
- VICE_PRESIDENT
- SECRETARY
- TREASURER
- CEO
- CFO
- COO
EXTRA_PROVINCIAL_CORPORATION_FOREIGN_CORPORATION_REGISTERED_IN_CANADA
- PRESIDENT
- VICE_PRESIDENT
- SECRETARY
- TREASURER
- CEO
- CFO
- COO
FOREIGN_PARTNERSHIP_REGISTERED_IN_CANADA
- PARTNER
COMMUNITY_CONTRIBUTION_COMPANY_FOR_PROFIT
- PRESIDENT
- VICE_PRESIDENT
- SECRETARY
- TREASURER
- CEO
- CFO
- COO
COMMUNITY_CONTRIBUTION_COMPANY_NOT_FOR_PROFIT
- OWNER
- PARTNER
- PRESIDENT
- VICE_PRESIDENT
- SECRETARY
- TREASURER
- CEO
- CFO
- COO
- MEMBER
Authorizations:
Request Body schema: application/json
| business_id required | string The Business ID that the account needs to belong to. This allows you to arrange the Accounts when they get created. |
| name required | string [ 0 .. 100 ] characters Account Name |
| sales_code_id | string [ 0 .. 50 ] characters Sales Code ID |
| sales_agent_id | string [ 0 .. 50 ] characters Sales Agent ID |
| sales_group_id | string [ 0 .. 50 ] characters Sales Group ID |
object (AccountCompanyRequestDto) Company Information - Supports both US (EIN) and Canadian (BN) applications | |
object (AddressRequestDto) Address Info | |
object (IndustryVolumeRequestDto) Industry & Volume Information | |
| ach_volume | integer <int32> Ach Volume Info |
object (ServicesDeliveriesRequestDto) Service Delivery Information | |
object (TransactionModesRequestDto) Service Delivery Information | |
Array of objects (MerchantOwnerCreationRequestDto) Owners Information | |
| processing_plan_id required | string Processing Plan id |
| terms_accepted | boolean Terms and Conditions are accepted or not |
object (PartnerDataDto) Partner Data Information | |
| country | string [ 0 .. 10 ] characters ^(US|CA)$ Default: "US" Country code - US or CA |
object User-defined fields as free-form JSON object |
Responses
Request samples
- Payload
{- "business_id": "string",
- "name": "string",
- "sales_code_id": "string",
- "sales_agent_id": "string",
- "sales_group_id": "string",
- "company": {
- "ownership_type": "GOVERNMENT",
- "category": "RETAIL",
- "ein": "string",
- "legal_name": "string",
- "dba_name": "string",
- "description": "string",
- "business_start_date": "2019-08-24",
- "website": "string",
- "timezone": "EST",
- "phone_number": "8005550100",
- "mcc": "7021",
- "stock_symbol": "string"
}, - "address": {
- "country": "US",
- "state": "AL",
- "city": "string",
- "zip_code": "35242",
- "address_line1": "string",
- "address_line2": "string"
}, - "industry_volume": {
- "avg_annual_volume": 999999999,
- "avg_ach_annual_volume": 999999999,
- "avg_ticket_amount": 99999,
- "high_ticket_amount": 0,
- "avg_ach_ticket_amount": 0,
- "ach_high_ticket_amount": 0
}, - "ach_volume": 0,
- "services_deliveries": {
- "same_day_delivery": 0,
- "one_week_delivery": 0,
- "two_week_delivery": 0,
- "one_month_delivery": 0,
- "more_than_one_month_delivery": 0
}, - "transaction_modes": {
- "in_person": 0,
- "online": 0
}, - "owners": [
- {
- "first_name": "string",
- "last_name": "string",
- "email": "test@example.com",
- "phone_number": "1234567890",
- "title": "OWNER",
- "ownership_percent": 50,
- "ssn": "123456789",
- "birth_date": "2019-08-24",
- "residence_address": {
- "country": "US",
- "state": "AL",
- "city": "string",
- "zip_code": "35242",
- "address_line1": "string",
- "address_line2": "string"
}, - "signer": true
}
], - "processing_plan_id": "string",
- "terms_accepted": true,
- "partner_data": {
- "paid_subscription": true,
- "merchant_joined": "2019-08-24T14:15:22Z",
- "backbook": true,
- "last_ip_address": "string",
- "sub_payor_name": "string",
- "request_credit_override": true,
- "prior_annual_volume": 999999999,
- "prior_avg_ticket": 999999999,
- "prior_high_ticket": 999999999,
- "six_mos_chargeback_rate": 0,
- "six_mos_refund_rate": 0,
- "redirect_url": "string"
}, - "country": "US",
- "user_fields": {
- "property1": { },
- "property2": { }
}
}Generate a boarding Application Link
Generate a shareable link for a boarding application that allows applicants to complete or submit the application through a hosted form. If you have configured your own Hosted Application domain, the link will be generated using your domain. Otherwise, the link will be hosted on Forward's platform. Prerequisites: A Processing Plan must be selected for the application before you can generate a link. Important: Application links can expire. Once a link expires, you will need to generate a new link to continue the application process. Use this endpoint when you want to share the application with applicants or allow them to complete the application form.
Authorizations:
path Parameters
| id required | string |
Responses
This is an object that represents a Forward Business associated with an Account. Every Account that you have must be associated with You can create a Business, fetch a particular Business or find all the Businesses that are associated to your Account.
Create a new Business
You can create a new Business that will be linked to your Account. We encourage you to complete all the fields while creating a new Business. Once you have created a Business you can start creating Applications and get associated Accounts.
Authorizations:
Request Body schema: application/json
| name required | string [ 0 .. 100 ] characters Business Name |
| contact_email | string Contact Email |
| contact_phone_number | string Contact Phone Number |
| contact_phone_extension | string Contact Phone Extension |
| contact_first_name | string [ 2 .. 50 ] characters Contact First Name |
| contact_last_name | string [ 2 .. 50 ] characters Contact Last Name |
Responses
Request samples
- Payload
{- "name": "string",
- "contact_email": "string",
- "contact_phone_number": "string",
- "contact_phone_extension": "string",
- "contact_first_name": "string",
- "contact_last_name": "string"
}A Contractor is a an entity in the platform's payment ecosystem. Using our Contractor entity you can setup split payments for a given transaction. The lifecycle of a Contractor is 1. A prospective contractor receives an application to apply as a Contractor, Note: Bank Account details is submitted with the Contractor Application. Note: you can create a new contractor application using link endpoint. 2. Once a contractor application is filled out the application gets submitted to underwriting. Note a Contractor can be Individual or Business. 3. If underwriting approves the application a new contractor entity comes into existence. The default state of the newly created Contractor is active. You can deactivate or toggle activate for a Contractor.
⚠️ DEPRECATED: This API is deprecated and will be removed in a future version. Please use the Payee API instead (payees).
Generate Contractor On-boarding Application Link Deprecated
Use this endpoint to create a new contractor application link. A contractor can select to be an individual or company. A company contractor will require some information link Owners information. ⚠️ DEPRECATED: Use payees/link instead.
Authorizations:
Request Body schema: application/json
| parent_id required | string Contractor Parent ID |
| parent_type required | string Default: "PARTNER" Enum: "PARTNER" "BUSINESS" Contractor Parent Type |
object (ContractorRequestExtBaseDto) Wrapper Company Payee Creation Information |
Responses
Request samples
- Payload
{- "parent_id": "string",
- "parent_type": "BUSINESS",
- "application_data": {
- "individual": {
- "first_name": "string",
- "last_name": "string",
- "address": {
- "country": "US",
- "state": "AL",
- "city": "string",
- "zip_code": "35242",
- "address_line1": "string",
- "address_line2": "string"
}, - "email": "string",
- "phone_number": "string",
- "ssn_encrypted": "string",
- "ssn": "string",
- "birth_date": "2019-08-24"
}, - "company": {
- "tax_id": "string",
- "name": "string",
- "legal_name": "string",
- "email": "string",
- "phone_number": "1234567890",
- "website": "www.example.com",
- "ownership_type": "PARTNERSHIP",
- "company_owners": [
- {
- "first_name": "string",
- "last_name": "string",
- "email": "string",
- "phone_number": "string",
- "residence_address": {
- "country": "US",
- "state": "AL",
- "city": "string",
- "zip_code": "35242",
- "address_line1": "string",
- "address_line2": "string"
}, - "ownership_percent": 0,
- "title": "OWNER",
- "ssn_encrypted": "string",
- "ssn": "string",
- "birth_date": "2019-08-24",
- "signer": true
}
], - "owners": [
- {
- "first_name": "string",
- "last_name": "string",
- "email": "string",
- "phone_number": "string",
- "residence_address": {
- "country": "US",
- "state": "AL",
- "city": "string",
- "zip_code": "35242",
- "address_line1": "string",
- "address_line2": "string"
}, - "ownership_percent": 0,
- "title": "OWNER",
- "ssn_encrypted": "string",
- "ssn": "string",
- "birth_date": "2019-08-24",
- "signer": true
}
], - "business_address": {
- "country": "US",
- "state": "AL",
- "city": "string",
- "zip_code": "35242",
- "address_line1": "string",
- "address_line2": "string"
}
}, - "documents_request": {
- "document_types": [
- "string"
], - "required": true,
- "received": true,
- "requested_date": "2019-08-24T14:15:22Z",
- "received_date": "2019-08-24T14:15:22Z",
- "comments": "string",
- "underwriter": "string"
}
}
}Find All Contractors by provided request Deprecated
Please provide the x-business-id so that all the Contractors can be retrieved for a given Business. If you don't provide this header you will get back all the Contractors that belong to you and none of our business specific Contractors. ⚠️ DEPRECATED: Use payees instead.
Authorizations:
query Parameters
required | object (ContractorExtFilterRequestDto) |
header Parameters
| x-business-id | string |
Responses
Get Contractor Application Link Status Deprecated
Here you can check the status of contractor application, if the contractor is created for an application you can also monitor is status with this endpoint. ⚠️ DEPRECATED: Use payees/application/{id} instead.
Authorizations:
path Parameters
| id required | string |
Responses
A Business on Forward can have one more Locations. Here you Create, Read, Update or Delete a Location for a Business.
Edit a Location
Business Locations are always editable, please keep this information updated as your information changes.
Authorizations:
path Parameters
| id required | string |
Request Body schema: application/json
| name required | string [ 0 .. 100 ] characters Location Name |
Responses
Request samples
- Payload
{- "name": "string"
}Find Locations
You can find all Locations that you have access to. Further filter on Business Location name and Business Id can be applied on the list of Locations.
Authorizations:
query Parameters
required | object (BusinessLocationFilterRequestExtDto) Business Location Filter Information |
Responses
Create a Location
This endpoint can be used to create a new Business Location only two fields are needed Business Id and Location Name.
Authorizations:
Request Body schema: application/json
| business_id required | string |
| name required | string [ 0 .. 100 ] characters Location Name |
Responses
Request samples
- Payload
{- "business_id": "string",
- "name": "string"
}Here you can find all Merchant Category Codes that are assigned to your Accounts. Please contact Forward support if you have any questions.
List all MCCs
Use this endpoint to list all of the MCCs that have been assigned to you. Please verify this information as it plays a key role in our payment processing flows, as well as the Application creation process.
Authorizations:
query Parameters
required | object (MccCodeFilterRequestDto) MC Codes Filter Request |
Responses
A Payee is a an entity in the platform's payment ecosystem. Using our Payee entity you can setup split payments for a given transaction. The lifecycle of a Payee is 1. A prospective payee receives an application to apply as a Payee, Note: Bank Account details is submitted with the Payee Application. Note: you can create a new payee application using link endpoint. 2. Once a payee application is filled out the application gets submitted to underwriting. 3. If our process approves the application a new payee entity comes into existence. The default state of the newly created Payee is active. You can deactivate or toggle activate for a Payee.
Generate Payee On-boarding Application Link
Use this endpoint to create a new payee application link. Note: All top-level fields in the request are optional. You can send an empty request body to generate a link without pre-populating any data. If you choose to provide application data, you can specify either an individual or company payee. Important: If you include application data, all required fields within that data must be properly completed. Individual Payee: If you provide individual payee information, all required fields (first name, last name, email, phone number, address, etc.) must be included and valid. Company Payee: If you provide company payee information, required fields like company name, legal name, email, website, and owner information must be properly completed.
Authorizations:
Request Body schema: application/json
object (PayeeRequestExtBaseDto) Payee Application Data | |||||
| |||||
Responses
Request samples
- Payload
{- "application_data": {
- "individual": {
- "first_name": "string",
- "last_name": "string",
- "address": {
- "country": "US",
- "state": "AL",
- "city": "string",
- "zip_code": "35242",
- "address_line1": "string",
- "address_line2": "string"
}, - "email": "string",
- "phone_number": "string"
}, - "company": {
- "name": "string",
- "legal_name": "string",
- "email": "string",
- "phone_number": "1234567890",
- "website": "www.example.com",
- "ownership_type": "SOLO_TRADER",
- "company_owners": [
- {
- "first_name": "string",
- "last_name": "string",
- "email": "string",
- "phone_number": "string",
- "residence_address": {
- "country": "US",
- "state": "AL",
- "city": "string",
- "zip_code": "35242",
- "address_line1": "string",
- "address_line2": "string"
}, - "ownership_percent": 0,
- "title": "OWNER"
}
], - "owners": [
- {
- "first_name": "string",
- "last_name": "string",
- "email": "string",
- "phone_number": "string",
- "residence_address": {
- "country": "US",
- "state": "AL",
- "city": "string",
- "zip_code": "35242",
- "address_line1": "string",
- "address_line2": "string"
}, - "ownership_percent": 0,
- "title": "OWNER"
}
], - "business_address": {
- "country": "US",
- "state": "AL",
- "city": "string",
- "zip_code": "35242",
- "address_line1": "string",
- "address_line2": "string"
}
}
}
}Deactivate an existing Payee
Deactivate a payee to temporarily disable it from being used in split payment transactions. A deactivated payee cannot receive payments as part of transaction splits, but the payee record is preserved and can be reactivated later. Use this when you need to temporarily stop payments to a payee without deleting their information, such as when a payee is on hold or under review.
Authorizations:
path Parameters
| id required | string |
Responses
Activate an existing Payee
Activate a payee to make it available for use in split payment transactions. An activated payee can receive payments as part of a transaction split. Note: The payee must have completed the identity verification process before it can be activated. Once activated, the payee will be in an active state and can be used in payment operations.
Authorizations:
path Parameters
| id required | string |
Responses
Find All Payees by provided request
Retrieve a paginated list of all payees associated with your Partner account. Use the request parameters to filter and paginate results. This endpoint is useful for viewing all available payees that can be used in split payment transactions.
Authorizations:
query Parameters
required | object (PayeeExtFilterRequestDto) |
Responses
Get an existing Payee By ID
Retrieve complete details about a specific payee by its unique identifier. This endpoint returns all payee information including status, contact details, and configuration. Use this to view payee details before including them in split payment transactions.
Authorizations:
path Parameters
| id required | string |
Responses
Find All Payee Applications by provided request
Retrieve a paginated list of all payee applications associated with your Partner account. Use the request parameters to filter and paginate results. This endpoint allows you to monitor all payee applications in various stages of the onboarding process, from pending to approved.
Authorizations:
query Parameters
required | object (PayeeApplicationFilterRequestDto) |
Responses
Get Payee Application Link Status
Retrieve the current status of a payee application. If a payee entity has been created from the application, you can also check the payee's status using this endpoint. Note: Webhooks are available to receive real-time notifications about payee application and payee status changes, eliminating the need for polling. This endpoint is useful for one-time status checks or when webhooks are not configured.
Authorizations:
path Parameters
| id required | string |
Responses
Processing Plans are key information that determines fees and payout processing at Forward. You can view, create, update a Processing Plan associated with your Accounts.
Find all Processing Plans
Here you can find all the Processing Plans, if you specify Name you can filter on specific Name as well.The Processing Plan data will be returned to you in a list.
Authorizations:
query Parameters
required | object (ProcessingPlanFilterDto) Processing Plan Filter |
Responses
Get a Processing Plan by id
Here you can review Processing Plan that has been created and verify the information is accurate. If there are any discrepancies in the Fees data please reach out as these play a key role processing payouts.
Authorizations:
path Parameters
| id required | string |
Responses
Update a User
You can keep information regarding your user updated here.
Authorizations:
path Parameters
| id required | string |
Request Body schema: application/json
| first_name required | string User First Name |
| last_name required | string User Last Name |
string User Email Address |
Responses
Request samples
- Payload
{- "first_name": "string",
- "last_name": "string",
- "email": "test@test.com"
}Create a Business User
Here you can create a user for a specific Business. Provide all the necessary details about the user. We will send an automated email out informing your user to setup a password and login. You can also generated a one time login link for this user.
Authorizations:
Request Body schema: application/json
| business_id required | string Business Id |
| first_name required | string User First Name |
| last_name required | string User Last Name |
| email required | string [ 0 .. 70 ] characters User Email |
Responses
Request samples
- Payload
{- "business_id": "string",
- "first_name": "string",
- "last_name": "string",
- "email": "string"
}