In addition to creating transactions via API, you can also create them:
- Manually using the Dashboard constructor.
- Automatically during onboarding of new applicants.
- Via transaction upload.
To create transactions in the Dashboard:
- Go to the Transactions page.
- Click Create transaction manually.
- From the drop-down list, select an applicant on behalf of whom you want to produce the transaction. When creating a Travel Rule transaction, select No applicant (Travel Rule only) and follow the instructions provided in this article.
- Switch between the simplistic (visual representation) form and JSON payload (digital data).
- When using a simplistic form, select the Use Case (a transaction type).
- Fiat — foreign currency transactions.
- Crypto transaction — cryptocurrency transfers.
- Gambling bet and Gambling limit change — bets and betting rules for gambling platforms.
- Select whether the transaction is inbound or outbound (for Fiat and Crypto transactions only).
- Enter the transaction information based on the transaction type.
- Fiat — amount, currency, payment details (the purpose of payment), beneficiary full name and external user ID, and the transaction date (custom or current).
- Crypto transaction — amount, asset (cryptocurrency), payment details (the purpose of payment), blockchain TXID, sender full name, external user ID, applicant wallet address, and the transaction date (custom or current).
- Gambling bet — amount, currency, result amount, bet type (sports, casino, poker, other), and the transaction date (custom or current).
- Gambling limit change — limit change type (deposit, loss, wager, session time, self-exclusion), amount, currency, period, and the bet change date (custom or current). Select the respective checkbox if you want the change to be reverted later.
- Set the custom transaction date by selecting the associated checkbox if necessary.
- Click Create transaction.
The option of creating KYC transactions during onboarding of new applicants can help you customize the risk policy, perform cross-checks, and calculate transaction risk score that affects the total applicant onboarding risk score.
When this option is enabled, every time a new applicant is being onboarded, the rules installed from the Basic Onboarding bundle are triggered and automatically applied to determine whether the applicant data such as email, phone number and/or IP address matches the rules parameters. For example, whether the email was created on a disposable platform or the phone has been used in suspicious transactions, and so on.
Once the applicant data is checked, you receive the transaction score, which in turn affects the applicant onboarding risk score. The applicant is approved, rejected, or delegated to you for review, depending on the results of multiple cross-checks described in the installed rules.
Mind the following:
- At least one of the rules from the Basic Onboarding bundle must be installed for the option to take effect.
- The option of creating KYC transactions during onboarding is mandatory for the applicant onboarding score calculation (based on the transaction score).
To enable the option of creating KYC transactions during onboarding:
- Open the verification level you want to add the option to, or create a new one.
- In the General section, expand More options.
- Select the Create KYC transactions during onboarding checkbox under Transaction monitoring settings.
- Click Save.
To send transactions as JSON, TXT, or CSV files:
- Go to the Transactions page.
- From the kebab menu, select Upload transactions.
- Select the Score saved transactions checkbox if you want your previously saved transactions to be scored.
- Drag and drop the file or select it on your computer.
- Click Upload.
Updated 5 days ago