Test and Launch


WePay’s Clear API deals with money movement. It’s not ideal to test with live credit cards outside of staging, as each transaction will be reviewed by risk, and will be charged to your platform. As such, this page will help you figure out what and how to test.

Magic Behavior

Staging lets you charge Credit Cards and bank accounts, without actually capturing funds. If you want to begin testing in a live environment (or test in stage without using actual Credit Cards), we offer Magic Headers and Magic Values.

Magic Headers are key/value pairs that you place in your headers for your API requests. Magic Headers simply simulate real life responses, and ignore any information you add to API requests, like request bodies.

In order to use Magic Headers, simply add the following key to the headers of a request:


With the appropriate value found here, depending on the specific user flow being tested.

Magic Values are values used inside POST requests to simulate API behavior, such as seeing a failure use case for identity verification.

Test KYC & Identity Verification


With KYC and Identity Verification, you’ll want to make sure you can simulate specific scenarios outside of the happy path use case, which is a Legal Entity and Account successfully onboarding to your platform without providing extra verification.

When you encounter these scenarios, make sure to refer back to the Onboard Merchants guide to see what information is needed.

Test Payments


For Payment Processing, you can test using both Magic Headers and Magic Values. If you want to test static responses, then Magic Headers are what you will use. If you want to test payments going through, with varied responses, then you will use Magic Values.

Find a full list of Magic Values here.

Let’s say you’re testing out paying via Credit Card or Payment Bank. Simply enter the values from the above table in your Payments Method call, and execute.

When testing payments, be sure to test:

  • A successful payment executed one-time.
  • A successful payment executed via delayed capture.
  • A failed payment for various reasons.
  • A successful micro deposit verification (for platforms supporting ACH).
  • A failed micro deposit verification (for platforms supporting ACH).

Test Payouts


Like Payments, when you test payouts, you have two different options. You can use Magic Headers or Magic Values. Find a full list of Magic Values here When testing payouts, be sure to do the following:

  • Test a payout to a merchant’s account.
  • Test a payout to a merchants account, that hasn’t enabled the capability yet.

Test Payment Operations


With Payment Operations, it’s important to simulate user flows like chargebacks. We currently support the response structures you get with Magic Headers.

If you want to simulate a specific chargeback where no funds are present, use Magic Values. Find a full list of Magic Values here

Be sure to test the following:

  • Test contesting a dispute.
  • Test conceding a disputed.
  • Test a successful refund.

Test Notifications


Notifications are Webhooks passed to you in real time. When you test other API calls, make sure to register for Notifications. If you need area to receive Webhooks outside your own server, use a tool like: https://requestbin.fullcontact.com/.

When you register your callback_uri, simply use a URL generated by the tool above. Then, make calls to the API, and trigger notifications.

Find notification testing paths here.

Certification to Live


With the Clear API product, you’re required to reach out to WePay to move to live. At minimum, you will need to sign a shared agreement between WePay and your platform.

In addition, WePay is defining a certification process that will require you to answer the following questions:

  • PCI scope: are you adequately prepared to handle the different levels of PCI scope?
  • Fee schedule: have you set a fee schedule to charge merchants the right amount? In addition, have you set a payout for your platform to receive funds?
  • Have you enabled Notifications on your platform?
  • Have you added Risk information to your API calls?
  • Have you built sufficient tooling for your Merchants to handle chargebacks and disputes?

Reach out to your WePay account manager to begin the process.

While the Basic Integration prepares you for a baseline Clear integration, it’s important to navigate to the Cookbooks and Resources section and prepare for more scenarios. Questions? Need help? Visit our support page!