WePay logo
      Nothing Found

Update capabilities

post/accounts/{id}/capabilities

This endpoint requires permission from WePay. The POST /accounts/{id}/capabilities call allows your platform to update an account's capabilities. The accounts resource allows your platform to create a new merchant account for each distinct business purpose.

SecurityappIdAuth and appTokenAuth
Request
path Parameters
id
required
string [ 1 .. 255 ] characters

ID of the merchant account, generated by WePay when the account is created.

query Parameters
is_expanded
boolean
Default: true
header Parameters
Api-Version
required
string
Example: 3.0
Content-Type
required
stringapplication/json
Example: application/json
Unique-Key
string
Request Body schema: application/json
object

Specify the capability being updated.

object

Specify the capability being updated.

Responses
200
Response Schema: application/json
resource
required
string

Helps organize information by identifying the resource type of the object data.

Value: Description
capabilities
id
required
string or null [ 1 .. 255 ] characters

A reference number your platform assigns to an Item.

path
required
string

The HTTP path of the resource. The path can be used to retrieve details about the resource and perform actions on it.

required
object

Details the owner resource and owner path.

api_version
required
string
object

Details an Account's Payments capability status, and reasons for a disabled status (i.e. enabled : false), if applicable.

object

Details an Account's Payouts capability status, and reasons for a disabled status (i.e. enabled : false), if applicable.

object

Details an Account's Terminals capability status, and reasons for a disabled status (i.e. enabled : false), if applicable. Note: If your platform does not have permission from WePay to use Card Present, then your merchants' terminal capability will never be enabled. This will not impact their ability to process web-based, card-not-present transactions.

object

Details an Account's onboarding status with Chase Merchant Services.

400

INVALID_PARAMS

403

NOT_AUTHORIZED

500

UNEXPECTED_ERROR

Request samples
application/json
{
  • "payouts": {
    • "application_block": {
      • "is_blocked": true,
      • "reason": "This is a sham!"
      }
    }
}
Response samples
application/json
{
  • "transaction_division_setup": {
    • "current_issues": [
      • {
        • "identity_verification": {
          • "path": "controller.personal_verification.documents",
          • "requested_documents": [
            • "passport",
            • "drivers_license"
            ],
          • "message": "we need to verify your date of birth"
          },
        • "issue_type": "identity_verification",
        • "target": {
          • "id": null,
          • "path": "/legal_entities/672b72f5-5136-4304-b553-ec7c8544b51e/verifications",
          • "resource": "verifications"
          }
        }
      ],
    • "enabled": true,
    • "upcoming_issues": { }
    },
  • "payments": {
    • "enabled": true,
    • "current_issues": [ ],
    • "upcoming_issues": { }
    },
  • "payouts": {
    • "enabled": false,
    • "current_issues": [
      • {
        • "issue_type": "application_block",
        • "application_block": {
          • "reason": "This is a sham!"
          },
        • "target": {
          • "resource": "accounts",
          • "id": "f779afd5-f860-43fb-9d19-d47d3b099bf3",
          • "path": "/accounts/f779afd5-f860-43fb-9d19-d47d3b099bf3"
          }
        }
      ],
    • "upcoming_issues": { }
    },
  • "terminals": {
    • "enabled": true,
    • "current_issues": [ ],
    • "upcoming_issues": { }
    },
  • "id": null,
  • "resource": "capabilities",
  • "path": "/accounts/f779afd5-f860-43fb-9d19-d47d3b099bf3/capabilities",
  • "owner": {
    • "id": "f779afd5-f860-43fb-9d19-d47d3b099bf3",
    • "resource": "accounts",
    • "path": "/accounts/f779afd5-f860-43fb-9d19-d47d3b099bf3"
    },
  • "api_version": "3.1"
}