WePay logo
      Nothing Found

Update a payout

post/payouts/{id}

The POST /payouts/{id} call allows your platform to update and add custom data to a payout. Payouts allow your merchants to receive their funds from your platform.

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

ID of the payout, generated by WePay when the payout is created.

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 or null

Any custom data your platform chooses to attach to this resource. The custom data must be key-value pairs and not contain any personally identifiable information (PII) or payment card (PCI) data.

Array of objects or null

Any rbit data your platform chooses to attach to this resource. The rbit data must be key-value pairs and can be an array of rbit objects.

Responses
200
Response Schema: application/json
id
required
string

ID of the payout, generated by WePay when the payout is created.

resource
required
string

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

Value: Description
payouts
path
required
string

Path of resource and resource ID.

required
object or null

Details the owner resource and owner path.

amount
integer

Amount in cents.

api_version
string
complete_time
integer or null <int64> >= 0

The time (in UNIX) the payout was completed.

create_time
integer <int64> >= 0

The time (in UNIX) when the payout was created.

currency
string

ISO 4217 currency code. Possible values include: CAD & USD. Note: as of today, currency supports a single value.

Enum: Description
USD

United States Dollar

CAD

Canadian Dollar

… 1 more
object or null

Any custom data your platform chooses to attach to this resource. The custom data must be key-value pairs and not contain any personally identifiable information (PII) or payment card (PCI) data.

object or null
object

Payout method associated with payouts.

Array of objects or null or null
Array of objects or null

Any rbit data your platform chooses to attach to this resource. The rbit data must be key-value pairs and can be an array of rbit objects.

reference_id
string or null [ 1 .. 255 ] characters

A custom reference ID for your platform to track the object. It can be any string.

status
string
Enum: Description
pending

WePay is currently processing this payout. See the pending_reasons structure for additional information.

completed

WePay has finished processing this payout. Note: Other bank institutions must also process payouts to bank accounts before the merchant will see the deposit in their account.

… 1 more
object or null

When a non-payment resource (i.e. recoveries or payouts) fails to process, fetch this transaction record in order to maintain accurate accounting of the merchant's balance.

object or null

When a payout has occurred, fetch this transaction record to account for the debit from the merchant.

400

INVALID_PARAMS

403

NOT_AUTHORIZED

500

UNEXPECTED_ERROR

Request samples
application/json
{
  • "custom_data": null
}
Response samples
application/json
{
  • "amount": 941,
  • "complete_time": 1510128604,
  • "create_time": 1510128004,
  • "currency": "USD",
  • "custom_data": {
    • "customer_id": "a65dbc451",
    • "reference_number": 436
    },
  • "failure_reason": null,
  • "id": "00000000-0000-0000-0000-00000a51d642",
  • "owner": {
    • "id": "be2b42e5-b808-40ae-9bbe-3291ab493f57",
    • "path": "/accounts/be2b42e5-b808-40ae-9bbe-3291ab493f57",
    • "resource": "accounts"
    },
  • "path": "/payouts/00000000-0000-0000-0000-00000a51d642",
  • "payout_method": {
    • "id": "00000000-6261-5553-0000-000000000bf2",
    • "path": "/payout_methods/00000000-6261-5553-0000-000000000bf2",
    • "resource": "payout_methods"
    },
  • "pending_reasons": null,
  • "resource": "payouts",
  • "status": "completed",
  • "txnr_failure": null,
  • "txnr_payout": {
    • "id": "00000000-0000-0000-0000-000000013003",
    • "path": "/transaction_records/00000000-0000-0000-0000-000000013003",
    • "resource": "transaction_records"
    },
  • "api_version": "3.0"
}