Submit Personal Banking Application

Creates and submits a personal banking services application for an individual — typically an agent or sole proprietor seeking Instant Funding or payment settlement services. Unlike the business banking endpoint, this one captures individual identity data rather than a full business profile. On success, a profileId is returned for subsequent status and notes lookups.

Endpoint

POST /api/v1/banking/submit/personal

Authentication

Basic HTTP Authentication required.
Encode username:password in Base64 and pass in the Authorization header:

Authorization: Basic {base64(username:password)}

When to use

Use this endpoint when onboarding an individual agent or sole proprietor who does not have a separate business entity but needs access to Instant Funding or payment processing settlement. It is the personal counterpart to POST /api/v1/banking/submit, which handles business banking applications.

Request Body

{
  "agentPayoutProfileId": 1082,
  "firstName": "Robert",
  "lastName": "Fitzgerald",
  "middleName": "James",
  "address": "750 Maple Street",
  "city": "Austin",
  "state": "Texas",
  "zip": "78701",
  "phone": "5125550234",
  "ssn": "523401987",
  "birthday": "1977-09-14T00:00:00Z",
  "email": "[email protected]",
  "agentId": 3381
}

Response

200 OK

{
  "data": {
    "profileId": 8104,
    "error": null
  },
  "requestId": 66318,
  "success": true,
  "error": null,
  "validationErrors": []
}

Error Codes

Common Mistakes

• Sending SSN with dashes (523-40-1987) — the field requires exactly 9 consecutive digits with no separators.
• Using state abbreviations (TX) instead of the full enum name (Texas) — the API validates against a specific enum list.
• Sending phone numbers with spaces, dashes, or country code prefixes — only 10 digits (or * wildcards for masked values) are accepted.
• Providing a ZIP code in ZIP+4 format (78701-1234) — only 5-digit ZIPs are accepted.
• Confusing agentPayoutProfileId (required, links to a payout account) with agentId (optional, internal agent identifier) — both may be needed if the agent context differs.

Related Endpoints

• POST /api/v1/banking/submit — Submit a full business banking application for a merchant entity
• GET /api/v1/banking/status — Check the approval status of a submitted banking application
• GET /api/v1/banking/notes/{profileId} — Retrieve reviewer notes for the application

Example

curl -X POST https://hq.staging.netevia.dev/api/v1/banking/submit/personal \
  -H "Authorization: Basic $(echo -n 'username:password' | base64)" \
  -H "Content-Type: application/json" \
  -d '{
    "agentPayoutProfileId": 1082,
    "firstName": "Robert",
    "lastName": "Fitzgerald",
    "address": "750 Maple Street",
    "city": "Austin",
    "state": "Texas",
    "zip": "78701",
    "phone": "5125550234",
    "ssn": "523401987",
    "birthday": "1977-09-14T00:00:00Z",
    "email": "[email protected]"
  }'