Necessary Account Settings
Wyre must manually configure the Users API on your master account. Please reach out to sales if interested.
The basic process looks like this:
• Create User
• Approve User by Scope
Call the Create User endpoint to create the user.
Approvals in the users system exist in the context of scopes. 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.
• To see the fields required for a specific scope, call Get User and pass the
scopes query parameter
• Identify any fields that are in
• Call Update User to submit this data to Wyre. Use masquerading
• Repeat until all required fields are in
OPEN fields have been
SUBMITTED and necessary KYC onboarding has been performed, the User Scope will move into
Now that your user is approved to transact, you may begin Using Transfers! Remember to use masquerading for requests made on behalf of your users. This simple pattern helps to firewall permission boundaries between users and your partner-level API credentials.
Users each have their own set of custodial 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.
|TRANSFER||General access to the Transfers API. Access to this scope is required for all transfers.|
|ACH||Access to create payment methods (attach bank accounts).|
KYC Onboarding URL
User Payment Method
|DEBIT_CARD_L2||Higher Limits Card Processing|
KYC Onboarding URL
|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.|
The field IDs your specific integration has to support depend on your integration type.
|Field Value||Field Type||Description|
|STRING||First name of the end user|
|STRING||Last name of the end user|
|STRING||The user's cellphone number including country code|
|STRING||The user's email address.|
|OBJECT||The user's residence address|
|STRING||The user's date of birth (YYYY-MM-DD)|
Updated about 1 year ago