/api/v1/banking/submit/personal

Time	Status	User Agent
Retrieving recent requests…

Time

Status

User Agent

Retrieving recent requests…

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

Field	Type	Required	Description
agentPayoutProfileId	integer (int32)	Yes	Payout profile ID for the agent — links this application to an existing payout account
firstName	string	Yes	First name (letters and spaces only, pattern: `[a-zA-Z\s]+`)
lastName	string	Yes	Last name (letters and spaces only, pattern: `[a-zA-Z\s]+`)
middleName	string	No	Middle name (letters and spaces only)
address	string	Yes	Street address (must begin with a number)
city	string	Yes	City name
state	string (enum)	Yes	Full state name, e.g. `California`, `NewYork`, `Texas`
zip	string	Yes	5-digit ZIP code (pattern: `^\d{5}$`)
phone	string	Yes	10-digit phone number, digits only (pattern: `^(\d
ssn	string	Yes	Social Security Number — exactly 9 digits, no dashes (pattern: `^\d{9}$`)
birthday	string (date-time)	Yes	Date of birth in ISO 8601 format
email	string	Yes	Email address for communications
agentId	integer (int32)	No	Internal agent ID if different from the payout profile agent

{
  "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

Field	Type	Description
data.profileId	integer	Newly created banking application profile ID — use for status and notes lookups
data.error	string	Error detail if profile creation failed
requestId	integer	Echo of the internal request ID
success	boolean	`true` if the application was submitted successfully
error	string	Top-level error message if `success` is `false`
validationErrors	array	Field-level validation errors with `field` and `error` properties

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

Error Codes

Code	When it happens
400	Required fields are missing, or field values fail validation patterns (e.g., SSN with dashes, abbreviated state, non-numeric ZIP)
401	Invalid or missing Basic Auth credentials
403	User does not have permission for this operation
500	Internal server error while submitting the profile

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]"
  }'