- User: the end-user originating the request
- Partner: You, the Wyre integrator!
- Field: A bucket for a specific piece of user data
- Scope: A specific segment of functionality on the Wyre platform
The basic process looks like this:
- Create User
- Get Approved
Call the create user API endpoint to create the user. This call will return a set of fields contextualized by the
scopes parameter provided. User creation also may include blockchain address generation if desired.
After the user is created, all user API calls require you to use masquerading on your requests. This simple pattern helps to firewall permission boundaries between users and your partner-level API credentials.
Approvals in the users system exist only in the context of scopes. The specific user requirements enforced for a given scope are determined by your partner agreement with Wyre. Because end-user requirements differ across available Wyre functionality, scopes are used to constrain the API based on the specific intent of a single user.
Broadly, to achieve user approval:
- Filter the fields returned by either create user or get user endpoints for those which are
- Collect data for one or more of these open fields to your end user
- Submit this data to Wyre
When there are no longer any
OPEN fields, the end user is done with their turn. Our system is diligently processing their information. After this stage:
- the user status may transition to
- or the user status may transition to
CLOSEDif fraud/compliance problems have been detected. Wyre customer support followup is required
- or the user status may transition back to
OPENif correctable problems were detected
Now that your user is approved, you may use the transfer API on their behalf! Remember to use masquerading for requests made on behalf of your users.
Users each have their own set of custodialized balances (including all our supported fiat and crypto). This is where funds are reflected which is sent to the blockchain addresses tied to the user. Users may be used as the source or destination via the transfer API to move and exchange these funds.
General access to the Transfers API. Access to this scope is required for all transfers.
Access to create payment methods (attach bank accounts) to Users
Higher Limits Card Processing
Waiting on data to be submitted to one or more fields.
This is the initial state before any information has been submitted, or if there were correctable problems with a previous submission.
Information has been fully submitted and is waiting on review from Wyre.
Information has been reviewed and accepted by Wyre
The Account has been closed and may not transact. Customer service followup is necessary for further actions.
A representation of the underlying KYC data. Actual format depends on the type of field
A message indicating the nature of a correctable problem. Accompanied by an
The field IDs your specific integration has to support depend on your integration type.
First name of the end user
Last name of the end user
the cellphone number of the account holder
the email address of the account holder
the residence address of the account holder
the date of birth of the person, e.g.
The field type is hard-coded to each field ID and determines the JSON format and upfront validation rules on it.
A full cellphone number including country code
A correctly formatted email address
An address object. Address format is:
Specifies a particular day. Format is