Tell us how often you would like to receive payouts by using the "period" drop down.

While this step isn't necessary to do before making API calls, it's a one-time set up, and lets you receive payouts daily (midnight settlement), weekly (every Monday), or monthly (first of the month). If these days are a bank holiday, it'll be the next day.

Visit our Partner Center guide to learn about business management features and functionalities the Partner Center has to offer.

Subscribe To API Notifications

Notifications are webhooks sent by the API to deliver information about your merchants, payment processing, and payment operations.

The lifecycle follows this general pattern:

1. Receive a notification from WePay about a payment, merchant, payout, or other operation.
2. Inspect content of the Notification Signature to ensure that the notification is intact and sent from WePay.
3. Inspect payload.create_time to determine chronology, not the event_time of the notification itself

If a Notification fails to reach your servers, we will attempt to retry following this pattern:

• 1st retry will happen 15 minutes after the initial attempt.
• 2nd retry will happen 30 minutes after the 1st retry.
• 3rd retry will happen 1 hour after the 2nd retry.
• 4th retry will happen 6 hours after the 3rd retry.
• 5th retry will happen 12 hours after the 4th retry.
• 6th retry will happen 24 hours after the 5th retry.

WePay defines "failing to reach your servers" as receiving any HTTP code other than 200 or 201. This also includes network retries. Due to potential retries, it is important to use the event_time value rather than receipt time to identify the order in which events occur.

When you transition to production on your dashboard, the WePay team will validate your Notifications implementation. Notifications are not stored permanently. If you haven't subscribed to notifications, you won't be able to retrieve older notifications once subscribed. However, once subscribed, Notifications are stored for 30 days.

Subscribe to API Notifications by making a POST /notification_preferences API request.

Recommended API Notification Subscriptions:

• accounts.created
• accounts.capabilities.updated
• payouts.failed
• disputes.created
• disputes.resolved
• legal_entities.verifications.updated
• payments.completed
• payments.canceled
• payments.failed

Add Rbits

We'll first walk through the inline flow. Let's say you're processing payments. All these calls accept an array of rBits, that you define inline.

For example, let's say you want to attach the Transaction Details object to your Payments. You've noticed a significant increase in payments, of which a bunch were spam. As such, you now add in Transaction Details as an rBit to get ahead of the problem.

{
  "rbits": [{
    "receive_time": 1367958263,
    "type": "transaction_details",
    "source": "user",
    "transaction_details": {
      "itemized_receipt": [
    	{
    	"amount": 105,
    	"currency": "USD",
    	"description": "Premium lawn service package",
    	"item_price": "100",
    	"project_name": "Lawn service at 123 Fake St.",
    	"quantity": 1,
    	"service_billing_method": "hourly_billing_at_project_rate"
    	}],
      "note": "returning customer, new payment method"
    }
  }]
}

You'll notice that at creation time of a new Payment, an rBit array was included. If you choose to do so, you can pack more rBits into the array.

It's also not necessary to do the inline flow, as you can first create a Payment, and update it with rBits after creation.

Next, we'll walk through the 2-step flow. Let's say you're onboarding merchants and you define rBits after onboarding.

For example, you want to attach the External Account object to merchant Accounts. Once you receive an Account ID from WePay, create an rBit by sending a POST /rbits request like this:

{
  "address": {
    "account_type": "facebook",
    "connections": "2000",
    "create_time": 1235635140,
    "feedback_score_percent_positive": 0.87,
    "feedback_scores_provided": "476",
    "is_partner_account": false,
    "uri": "facebook.com.merchantblob"
  },
  "associated_resource": {
    "id": "{merchant-account-id}", // insert the merchant's account ID here
    "resource": "accounts"
  },
  "receive_time": 1367958263,
  "source": "guidestar",
  "type": "address"
}'

View the Full API reference to see where you can add rBits. In general, the more you add to your Accounts and Payments, the better overall experience and minimization of loss for your end merchants and payers.