# API Reference Source: https://docs.truust.io/api-reference Complete reference for the Truust REST API v2.0 ## Overview The Truust API is organized around REST. All requests must be made over HTTPS to: * **Production:** `https://.truust.io/2.0` * **Sandbox:** `https://-sandbox.truust.io/2.0` ## Authentication All endpoints require a Bearer token using your account's **Secret Key**: ``` Authorization: Bearer {your_secret_key} ``` Your API keys are available in the Dashboard under **Account Settings → API Developers**. # Accept Order Source: https://docs.truust.io/api-reference/accept-order POST /orders/{id}/accept Seller accepts the order, triggering the payout process. # Cancel Order Source: https://docs.truust.io/api-reference/cancel-order POST /orders/{id}/cancel Cancels an order and refunds the buyer if a payin was made. # Cancel Pre-Authorization Source: https://docs.truust.io/api-reference/cancel-pre-auth POST /payins/{id}/cancelpreauth Cancels an `AUTHORIZED` (pre-authorized) payin without capturing funds. # Cancel Subscription Source: https://docs.truust.io/api-reference/cancel-subscription PUT /subscriptions/{id}/cancel Cancels an active subscription. No further charges will be made. # Create Account Source: https://docs.truust.io/api-reference/create-account POST /accounts Registers a new merchant account and its associated manager. # Create Bank Account Source: https://docs.truust.io/api-reference/create-bank-account POST /bankaccounts Registers a bank account for a customer (or the authenticated account). Use `GET /bankaccounts/validation` first to obtain the required fields for the given currency and country. # Create Bundle Source: https://docs.truust.io/api-reference/create-bundle POST /bundles Creates a new product bundle that can be linked to orders. # Add Card to Customer Source: https://docs.truust.io/api-reference/create-card POST /customers/{uuid}/cards Adds a card to a customer. The behaviour depends on `payin_type`: - `DCP`, `DCP_AUTH`: tokenizes a card. The response includes a `tokenization_link` the customer must visit to enter the card details. - `STRIPE`: issues a virtual card against `wallet_id`. See [Stripe Authorization](/guides/stripe-authorization). - `M2P_ISSUING` (only when card issuing is enabled): issues a card linked to a wallet previously created with `POST /wallets` and `type: M2P_ISSUING`. Issuance is asynchronous: the card is returned with `confirmed: false` and becomes `confirmed: true`, with the issuer token in `gateway_reference_id`, once the issuer confirms it. # Create Customer Source: https://docs.truust.io/api-reference/create-customer POST /customers Creates a new customer (buyer or seller). If a customer with the same email/phone already exists for this account, the existing record is updated and returned. Either `email` or `phone` (with `prefix`) is required. # Add Address to Customer Source: https://docs.truust.io/api-reference/create-customer-address POST /customers/{uuid}/addresses # Create KYC for a Customer Source: https://docs.truust.io/api-reference/create-customer-verification POST /customers/{uuid}/verify Submits KYC (Know Your Customer) identity verification information for a customer. Supported types: `NATURAL`, `SOLETRADER`, `LEGAL`. For `LEGAL` type, `legal_name`, `representative_name`, `representative_email` and `representative_phone` are required. # Create Order Source: https://docs.truust.io/api-reference/create-order POST /orders Creates a new escrow payment order. `buyer_id` and `seller_id` are required (both customers must exist). Once created, the order has a `buyer_link` and `seller_link` for the payment flow. # Create Payin Source: https://docs.truust.io/api-reference/create-payin POST /payins Creates a payin (payment intent) for an order. Requires `order_id` and either `type` or `gateway_id`. For card payments, the response includes a `direct_link` to the payment page. For bank wire payments, the response includes bank transfer details in `provider`. # Create Payout Source: https://docs.truust.io/api-reference/create-payout POST /payouts Creates a payout to transfer funds from a paid order to the seller. Requires the order to not yet be released. The destination is either a `wallet_id` or a `bankaccount_id`. # Create Subscription Source: https://docs.truust.io/api-reference/create-subscription POST /subscriptions Creates a recurring payment subscription. The first order is created immediately; subsequent orders are triggered on the defined schedule. # Create Wallet Source: https://docs.truust.io/api-reference/create-wallet POST /wallets Creates a new wallet for a customer or the authenticated account. # Delete Card Source: https://docs.truust.io/api-reference/delete-card DELETE /cards/{uuid} Removes a tokenized card from the customer. # Get Current Account Source: https://docs.truust.io/api-reference/get-account GET /accounts/me Returns the authenticated account's details. # Get Account Fees Source: https://docs.truust.io/api-reference/get-account-fees GET /accounts/fees/{currency} Returns the wallet with balance and fee information for the specified currency. # Get Bank Account Source: https://docs.truust.io/api-reference/get-bank-account GET /bankaccounts/{uuid} # Get Bank Account Validation Source: https://docs.truust.io/api-reference/get-bank-account-validation GET /bankaccounts/validation Returns the required fields and validation rules for a bank account given a currency, country, and type. # Get Bundle Source: https://docs.truust.io/api-reference/get-bundle GET /bundles/{bundle_id} Returns the details of a specific bundle. # Get Card Source: https://docs.truust.io/api-reference/get-card GET /cards/{uuid} # Get Customer Source: https://docs.truust.io/api-reference/get-customer GET /customers/{uuid} # Get Customer Address Source: https://docs.truust.io/api-reference/get-customer-address GET /customers/{uuid}/addresses/{address_uuid} # Get KYC Verification for a Customer Source: https://docs.truust.io/api-reference/get-customer-verification GET /customers/{uuid}/verification Returns the current KYC verification record associated with the customer. # Get Order Source: https://docs.truust.io/api-reference/get-order GET /orders/{id} # Get Order Payin Source: https://docs.truust.io/api-reference/get-order-payin GET /orders/{id}/payin Returns the payin associated with the order. # Get Order Payout Source: https://docs.truust.io/api-reference/get-order-payout GET /orders/{id}/payout Returns the payout associated with the order. # Get Payin Source: https://docs.truust.io/api-reference/get-payin GET /payins/{id} # Get Payout Source: https://docs.truust.io/api-reference/get-payout GET /payouts/{id} # Get Refund Source: https://docs.truust.io/api-reference/get-refund GET /refunds/{id} # Get Subscription Source: https://docs.truust.io/api-reference/get-subscription GET /subscriptions/{id} # Get Verification Source: https://docs.truust.io/api-reference/get-verification GET /verifications/{uuid} # Get Verification Document Source: https://docs.truust.io/api-reference/get-verification-document GET /verifications/{uuid}/documents/{document_uuid} # Get Wallet Source: https://docs.truust.io/api-reference/get-wallet GET /wallets/{uuid} # List Orders for a Bundle Source: https://docs.truust.io/api-reference/list-bundle-orders GET /bundles/{bundle_id}/orders Returns a paginated list of orders associated with the specified bundle. # List Bundles Source: https://docs.truust.io/api-reference/list-bundles GET /bundles Returns a paginated list of all product bundles. # List Customer Addresses Source: https://docs.truust.io/api-reference/list-customer-addresses GET /customers/{uuid}/addresses # List Customer Bank Accounts Source: https://docs.truust.io/api-reference/list-customer-bank-accounts GET /customers/{uuid}/bankaccounts # List Customer Cards Source: https://docs.truust.io/api-reference/list-customer-cards GET /customers/{uuid}/cards # List Customer Subscriptions Source: https://docs.truust.io/api-reference/list-customer-subscriptions GET /customers/{uuid}/subscriptions # List Customer Wallets Source: https://docs.truust.io/api-reference/list-customer-wallets GET /customers/{uuid}/wallets # List Customers Source: https://docs.truust.io/api-reference/list-customers GET /customers Returns a paginated list of customers associated with the authenticated account. # List Expired Bundles Source: https://docs.truust.io/api-reference/list-expired-bundles GET /bundles/expired Returns a paginated list of all expired product bundles. # List Orders Source: https://docs.truust.io/api-reference/list-orders GET /orders # List Payins Source: https://docs.truust.io/api-reference/list-payins GET /payins # List Payouts Source: https://docs.truust.io/api-reference/list-payouts GET /payouts # List Refunds Source: https://docs.truust.io/api-reference/list-refunds GET /refunds # List Subscriptions Source: https://docs.truust.io/api-reference/list-subscriptions GET /subscriptions # List Verification Documents Source: https://docs.truust.io/api-reference/list-verification-documents GET /verifications/{uuid}/documents # List Verifications Source: https://docs.truust.io/api-reference/list-verifications GET /verifications # List Wallet Transactions Source: https://docs.truust.io/api-reference/list-wallet-transactions GET /wallets/{uuid}/transactions # List Wallets Source: https://docs.truust.io/api-reference/list-wallets GET /wallets Returns a list of all wallets associated with the authenticated account. # Refund Payin Source: https://docs.truust.io/api-reference/refund-payin POST /payins/{id}/refund Issues a partial or full refund for a confirmed payin. Only supported payment methods can be refunded. For bank wire payins, a `bankaccount_id` is required to specify the refund destination. # Reimburse Order Source: https://docs.truust.io/api-reference/reimburse-order POST /orders/{id}/reimburse Issues a partial or full reimbursement for a paid order via wallet credit. # Request to Pay Source: https://docs.truust.io/api-reference/request-to-pay POST /payins/{id}/request Sends a payment request notification to the buyer for open-banking or request-to-pay type payins. # Request Verification Review Source: https://docs.truust.io/api-reference/request-verification POST /verifications/{uuid}/request Submits a verification with `CREATED` status for manual review. # Send Order Receipt Source: https://docs.truust.io/api-reference/send-order-receipt POST /orders/{id}/receipt Sends an email receipt to the buyer. # Submit Verification (KYC) Source: https://docs.truust.io/api-reference/submit-verification PUT /verifications/{uuid} Submits KYC information for a customer. Supported types are `INDIVIDUAL`, `SELFEMPLOYEE`, and `LEGAL`. For `LEGAL` type, representative information is required. # Sync Payin Status Source: https://docs.truust.io/api-reference/sync-payin PUT /payins/{id} Forces a status refresh by querying the payment provider. Useful for polling. # Sync Payout Status Source: https://docs.truust.io/api-reference/sync-payout POST /payouts/{id}/update Forces a status refresh for a confirmed payout. # Update Account Source: https://docs.truust.io/api-reference/update-account PUT /accounts/me Updates settings for the authenticated account. Accepts all parameters from Create Account plus the ones listed here. # Update Bundle Source: https://docs.truust.io/api-reference/update-bundle PUT /bundles/{bundle_id} Updates an existing bundle's properties. # Update Customer Source: https://docs.truust.io/api-reference/update-customer PUT /customers/{uuid} # Update Customer Address Source: https://docs.truust.io/api-reference/update-customer-address PUT /customers/{uuid}/addresses/{address_uuid} Only the `metadata` field can be updated on an existing address. # Update Order Source: https://docs.truust.io/api-reference/update-order PUT /orders/{id} Updates an order's details. After payment, only `metadata`, `fee_value`, and `fee_percent` can be changed. # Update Verification Document Source: https://docs.truust.io/api-reference/update-verification-document PUT /verifications/{uuid}/documents/{document_uuid} Updates the content or type of an existing KYC verification document. # Update Wallet Source: https://docs.truust.io/api-reference/update-wallet PUT /wallets/{uuid} Updates the `tag` or `metadata` of a customer wallet. # Upload Verification Document Source: https://docs.truust.io/api-reference/upload-verification-document POST /verifications/{uuid}/documents Uploads a KYC document for a verification. The `content` field must be a base64-encoded image. Supported `type` values: `IDENTITY_PROOF`, `REGISTRATION_PROOF`, `ARTICLES_OF_ASSOCIATION`, `SHAREHOLDER_DECLARATION`, `ADDRESS_PROOF`, `TAX_VERIFICATION`, `BUSINESS_ADMINISTRATOR_ID`, `COMPANY_REGISTRATION_PROOF`, `BANK_VERIFICATION`. # Validate Order Source: https://docs.truust.io/api-reference/validate-order POST /orders/{id}/validate Releases funds from escrow to the seller. If `auto_accept` is true, the acceptance step is skipped. Moves the order to `RELEASED` status. # Verify Account Source: https://docs.truust.io/api-reference/verify-account POST /accounts/verify Submits KYC (Know Your Customer) information for the authenticated account. Use `NATURAL` for individuals and `LEGAL` for companies. For `LEGAL` type, representative information is required. # The Dashboard Source: https://docs.truust.io/dashboard > Stay on top with your single source for tracking and analyzing your transactions, customer data and revenue. *** ## Overview All accounts have access to a personalized dashboard from which to perform all operations. The easiest way to use our services is with our Dashboard. You can create orders, track transactions and manage all order activity. ## Orders Truust works with the concept **orders**. Orders are the main entities with which our tool works. An order is **a transaction associated with a buyer and a seller**, identified by their phone numbers or email addresses. Each order will end up having associated at least one Payin (incoming money) and one or more Payouts (outgoing money). To create orders is necessary the information of the product, the information of the buyer and the information of the seller. You do not have to understand order as a product. An order should be understood as **a unique access to a payment gateway** with stable actors and fixed values. *Other industry names: Transaction, Checkout* \_\_ ### List all Orders ## Order Actions ### Create and Edit Orders To start creating orders follow the steps below: 1. Go to the orders page from the menu on the left of the page. Click “Orders”. 2. Once on the page, click on the “New” button at the top right of the page. A screen will open with the 3 steps necessary to generate the Order. Orders can be created when we know the seller and the buyer, if we do not have the information, we must use the "bundles" functionality (explained later in this document). #### Step 1: Order – Main Details The first screen refers to the data of the product or service. * **Name**: Write the name of the product or service. It will be the name that will be displayed on the payment screen, make sure it is recognizable by users. * **Account**: select the account from which you want to make the transaction. Remember that a user can create several accounts under the same user, for example, a business with different locations or an entrepreneur with different businesses. * **Amount**: specify in this field the amount of money to be requested for the product or service. The value of the transaction will be in euros. We have *additional information* that we can add to the order and that can be of great help to us to organize our orders internally. * **Image:** add an image to the product or service. * **Tag:** to relate the order with a tag that allows us to locate it easily (only visible internally). * **Fee:** you can indicate a Fee for a specific order that overwrites the one configured by default in your account. The Fee can be specified both in percentage and in absolute value. We will go into detail with the Fees in the account configuration section. Once you have completed the screen, click on the “Next” button. #### Step 2: Buyer – Payer Details On this screen, you must enter the purchaser data. * **Buyer Prefix**: the prefix of the buyer’s telephone. * **Buyer Phone**: the buyer’s telephone number. * **Buyer Confirmation URL**: page to which we will redirect the buyer once the payment has been completed. Web addresses should start with http or https. If you don't have any we will use our default page with your logo. * **Buyer URL Error**: Page where we will redirect the buyer if there is any problem with the payment. Web addresses should start with http or https. If you don't have any we will use our default page with your logo. Once completed click on the “Next” button. #### Step 3: Seller – Payee Details In this screen enter the data of the seller. * **Seller Prefix**: the seller’s telephone prefix. * **Seller Phone**: the phone number of the seller. * **Seller Confirmation URL**: page where we will redirect the seller once we have collected the payment information. Web addresses should start with http or https. If you don't have any we will use our default page with your logo. * **Seller Error URL**: Page where we will redirect the merchant if there is a problem collecting payment information. Web addresses should start with http or https. If you don't have any we will use our default page with your logo. Once completed click on the "Create Order" button. ### Cancel and Refund an Order Refunds are the term that explains when there is a lost dispute over a transaction and a refund must be made to the buyer. ### Validate an Order It's the action you take to release the money in the seller's account. This action can only be performed when the payment has been confirmed by Redsys and the merchant has entered their details into the platform. ### Block and Unblock an Order You can block an order to stop from releasing the payment to the seller. This dashboard functionality is very useful, for exemple, for transactions that may be suspicious of malpractice or when a return is requested and thus block the outflow of payment until the product has been returned and verified. When executing **"Block order"** the process will be stopped indefinitely until we **"Unblock order"**. Instructions: **How to block an order** 1. Sign in to your [Truust account](https://dashboard.truust.io/login). 2. From the order section, click the **\[···]** menu on the right of the order you want to block. 3. Then click **Block order**. \ A notification confirming the blocking action will be shown on the screen, and the order status will change to **"Blocked release"**. The order will remain blocked till the unblock action is done. Instructions: **How to unblock an order** 1. Sign in to your [Truust account](https://dashboard.truust.io/login). 2. From the order page, click the **\[···]** menu on the right of the order you want to unblock 3. Then click **Unblock order**. \ A notification confirming the unblocking action will be shown, and the order status will change to its previous status. ### Search and Sort Use the search funcionality to find payments, buyers, sellers, accounts, status and more. You can use the Truust mechanism available in the Dashboard to look up information about: * ID * Name * Tag * Account * Status * Buyer Code * Buyer Phone * Buyer Email * Seller Code * Seller Phone * Seller Email * Metadata * Created At After performing a search you see all the results matching with your query. From the resulting data you can click **"Order by"** or **"Sort"** to use our advanced filter options. ### Reporting When you perform a search you can export the results in a csv file to build your own database. ### Add a Bank Account for a Payout ## Payins ### List all Payins Payins are the payments made by buyers, the inflows of money. To access the Dashboard Payins screen follow the instructions below. 1. Sign in to your [Truust account](https://dashboard.truust.io/login). 2. Click on the **“Payins”** option on the left menu. Once the buyer has made the payment, it will be listed in this section. ## Payouts ### List all Payouts Payouts are the payments we make to the sellers, they are the payments that come out of the escrow account, the outflows of money. To access the Payouts page follow the instructions below. 1. Sign in to your [Truust account](https://dashboard.truust.io/login). 2. Click on the **"Payout"** option on the left menu. Every time a payment is done to he seller, it will be listed in this section. ## Products ### List all Products ### Create and Edit Products A **Product** is a grouping of orders with its own payment link, can be a product, a service or a joint financing campaign. **Products** allow you to sell several quantities of the same product with a single link or generate a campaign associated with a deadline. Orders can only be created when we can identify both parties so working with **Products** is the best alternative when the buyer and/or seller of the transaction is unknown. Instructions: **How to create a Product** 1. Sign in to your [Truust account](https://dashboard.truust.io/login). 2. Click on the **"Products"** option on the left menu. 3. Click on the "New" button. 4. Next, fill in the following fields to create a new product: * **Name**: write the name of the product. It will be the name that will be shown on the payment screen, make sure it is recognizable by users. * **Account**: select from the account that you want to make the transaction. * **Amount**: specify in this field the amount of money that will be requested in each order. * **Currency**: specifies the currency that will be used for each order. * **Description**: adds a brief description of the product. * **Image**: attach an image for the product. 5. Once completed click on the **"Create product"** product button. **How to edit a Product** 1. Sign in to your [Truust account](https://dashboard.truust.io/login). 2. Click on the **"Products"** option on the left menu. 3. From the Products page, click the **\[···]** menu on the right of the product you want to edit. 4. Change the information you need and click the save button. # Developers Source: https://docs.truust.io/developers > Get up and running with our API and other tools and start developing your Truust integration. *** ## Quick Start ### Getting API Keys There are several different identifiers associated with your Truust account. Here are some important ones you'll need to know. The public and secret keys together make up your account's API keys. Each account associated with Truust will have their own set of API keys, which they can change or rotate at any time for added security. Because this affects your integration, it should be done with caution. **IMPORTANT** Sandbox API keys are different from those in the production environment, so they must be updated in your code by your developers when switching between environments. More information about switching environments is available in our developer docs. #### Public key This is your account-specific public identifier. Each account associated with Truust will have its public key. To find your public key: * Log into either the production Dashboard or the sandbox Dashboard, depending on which environment you are working in * Click on the "Accounts Settings" button from your "Accounts" page list * Click the "API Developers" tab from the top menu * Scroll to the API Keys section and you will see the "Public Key" value #### Secret key This is your account secret identifier. Each account associated with Truust will have its secret key. Your secret key should not be shared outside the use of an API call – even with us. To find your secret key: * Log into either the production Dashboard or the sandbox Dashboard, depending on which environment you are working in * Click on the "Accounts Settings" button from your "Accounts" page list * Click the "API Developers" tab from the top menu * Scroll to the API Keys section and you will see an empty "Secret Key" field * Click the "Reveal" button located next to the Secret Key field Your secret key will be revealed in the Secret Key field on the same page. ### Environments The environment specifies where requests via the API should be directed – sandbox or production. Because you have a different set of API keys for each environment, you'll need to update your code depending on which environment you're working in. There are both production and sandbox environments for the API. The URL endpoints will be: * `https://-sandbox.truust.io/2.0` - Testing environment * `https://.truust.io/2.0` - Live production environment ## Webhooks Truust can send webhook events that **notify your application any time an event happens on your account**. This is especially useful for events that are not triggered by a direct API request, like order status change and many user actions. This mechanism is also useful for services that are not directly responsible for making an API request, but still, need to receive the response from that request. You can register webhook URLs and the attached event and we will notify you any time that event happens in your account. When the event occurs we will create a request containing **all the relevant information about what just happened**, via an HTTP `POST` request, to any endpoint URLs that you have defined in your account´s Webhooks settings. Webhooks are necessary only for behind-the-scenes transactions. Most requests (e.g., creating links) generate results that are reported synchronously to your code. These do not require webhooks for verification. To configure a webhook, you'll need to: 1. Create a webhook destination URL on your server 2. Create a new webhook in the Dashboard by entering your webhook destination URL and selecting at least one type of event for the webhook to fire on 3. Set up your server to parse incoming webhooks 4. Test your webhook handling code ### Notifications Here is a complete list with all the available notifications we will trigger for your account: * `Order Published` - The order has been successfully paid * `Order Failed` - There has been an error completing the payment * `Order Accepted` - The order has been accepted by the seller or automatically settled * `Order Rejected` - The order has been rejected by the seller * `Order Cancelled` - The order has been canceled for any reason * `Payout Created` - The payout associated with the order, has been created and we have the information needed to proceed with the payout * `Order Released` - The order has been released and we have transferred the funds to the assigned payout account ### Registering the Webhook Endpoint To create a webhook: 1. Log into the Dashboard corresponding to the environment you want to setup 2. Click on the Webhooks option on the side-menu 3. Click the Create New Webhook button 4. Provide your destination URL and your selected notification 5. Click the Create Webhook button When adding a webhook in the Dashboard, you'll need to provide a destination URL using a valid HTTPS path. This URL will receive all webhook notifications as POST requests and must be a publicly accessible URL on your site You can create multiple webhook destination URLs to route certain webhook notifications to specific endpoints. ## API Reference If you need an extensive integration and apply your own rules, you can access our services via API. To review our technical API Reference, visit the following link: > [API Reference](/api-reference) Our technical team is here to help. If you are a company with more complex technical needs, contact us at [hello@truust.io](mailto:hello@truust.io). ## Connectors Connectors # Getting Started Source: https://docs.truust.io/getting-started > Truust helps you create any type of payments flow—from e-commerce to split payments and everything in between ## Overview We offer a variety of products that make it easy for you to accept payments in your app or website. You’ll interact with us in three ways: 1. The Dashboard 2. The Application Programming Interface (API) 3. The Hosted Checkout ### The Dashboard The Dashboard is our user-friendly interface focused on the tools you need to keep your business running smoothly – allowing you to manually **set up orders, manage transactions, pull reports and more**. [Learn more about the Dashboard](/dashboard). ### The API The API is the architecture of our gateway – our complete set of code that powers everything we do, from payments to customer management. To integrate with Truust, your developers will update the existing code for your website or mobile app to make requests to our API, allowing you to **automate processes and customize the way you interact with the gateway**. Our [developer docs](/developers) will guide your developers through everything they'll need for complete integration. ### The Hosted Checkout The Hosted Checkout is an immediate way to enjoy the full power of Truust's API through a much easier integration. Simply get the order's `buyer_link`, which can be: * Embedded in an iframe within your website or application * Shared with the customer through any channel such as: Email, SMS, WhatsApp, Facebook Messenger, Instagram, etc. to get paid. [Learn more about the Hosted Checkout](/hosted-checkout) ## Environments There are two Dashboard and API environments: * [Sandbox Dashboard](https://dashboard-sandbox.truust.io/): Testing environment * [Production Dashboard](https://dashboard.truust.io/): Live production environment Both environments are mutually exclusive; **they do not interact with each other**, and it is possible to have different login credentials for each environment. **Your sandbox account is not linked to your production account in any way**. Nothing created in the sandbox will transfer to production. This includes processing options and recurring billing settings. Your login information, account settings and API keys will also be different. ## Accounts Accounts are the different groups with which you can organize your orders. Normally, an **account will correspond to the business** with which you want to use our platform. ### Registering an Account The first step to start working with us is **registering your account into our platform**. Remember that we have two environments available for you, so our recommendation is to **register first on the Sandbox environment to test the platform**. Once you are satisfied and understand all the basic details of our tool, you are ready to register on the Production environment. To create your first account, access to the following links: * [Sandbox Registration](https://dashboard-sandbox.truust.io/register): Testing environment * [Production Registration](https://dashboard.truust.io/register): Live production environment Where you will be asked to complete your user details. If the registration is successful, you will be redirected to the following page to create your first account. ### Your Account A screen with all options related to managing your Truust account will be displayed. * **Business Name**: It will be your account name. It will be your public identification, so make sure is an understandable reference to your users. * **Logo**: Company Logo. It will be displayed on your checkout page if you use the payments links feature. * **Payment Method**: Payment method that your customers will use to pay for your orders by default. You can set the individual payment method later creating the order. * **Fees:** commission value that will be applied by default to your transactions. You can indicate this commission in two ways: as a percentage and as an absolute value. Again, remember that you can set the individual fees for an individual payment when creating the order. To edit later your account, click on the **"Accounts"** option in the left sidebar. Then, click the **"Accounts Settings"** button for the account you want to set up. ### Multiples Accounts You can create additional Truust accounts associated with your email address. You might create some accounts yourself, and might be given access to other accounts as a team member. To create a new account, click on the name of your current Truust account at the lower-left corner, and select **New account**. You must use separate Truust accounts for projects, websites, or businesses that operate independently from one another. When you activate a new account, it is subject to Truust’s standard policies and pricing—it does not inherit any special status or other similar considerations that may apply to your existing account. Using additional accounts has several benefits: * **Separate tax and legal entity information:** Each account can only be associated with the tax ID and legal entity of one business. If you operate multiple businesses that have separate tax ID information (e.g., separate legal entities), you must create additional accounts for each. * **Unique statement descriptor and public business information**Using the same Truust account for separate businesses can confuse the public business information used is the same for both. For example, a customer who purchases from your business “XYZ” may see a charge from your business “ABC” on their statement, potentially resulting in a dispute. Each additional account has its public information to accurately describe your business and payments. * **Easier reporting and reconciliation**Separating the payments processed by your businesses make it easier to find payments, create and export reports, and reconcile payouts to your bank account. * **Payouts to separate bank accounts**Each additional account can use a separate bank account for payouts (although you can use the same bank account if you wish). If you need to create many new accounts—or provision accounts automatically—while maintaining centralized reporting and management, you may wish to consider using tags instead of using multiple conventional Truust accounts. ### Team Members and Roles Each account can have several team members with different roles and permissions. Our tool becomes the portal to include all the participants from your company in the process. For example, you can have a customer service profile, consulting our panel and reviewing the status of orders and this way giving support to your customers. You can also access this screen by clicking on **"Team Members"** in the left menu. In this screen you will be able to carry out all the operations related to the team members of your account: * Add a Team Member to your account * Edit current Team Members * Delete a Team Member #### Add a Team Member Click the "Create Team Member" button at the top right of the screen. Fill in the fields to create a new user. * **Name**: Name of the new user. * **Role**: the role we give it. * **Manager**: manages the users of the account (add, delete users and assign permissions). * **Customer Service**: has reduced permissions. You can see the data but not modify it. * **Email**: Email of the new user. * **Countries**: country or countries in which the new user will operate. * **Accounts**: account to which we give access. ### Account Activation To start working with Truust you must verify your account by providing your data, product/service data, and company legal data.