Sandbox environment

Base endpoints for sandbox environment:

API Base URL

All calls to our API should start with this specific URL: https://api.sandbox.finrax.com

Key for checking the authenticity of a Finrax callback on the sandbox environment:

MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAp8TwRhmscDIAnxihhf+KrFgFG0niwgys+j6bTPeOiOuQ5WEekoysmBTeyBTUrIBHtY11aw9VtQSDkMGu3/YmO0RZTKrZ0JbQ3HMIa7kCdETlp6vieE6GTZE/xMpj8lBHrcetECbjOGNi/qE7sd1gnfoxB2BMlxyvw15kQwimSrSx/w+VjhCe7wcE+gNEa7UJV1CE7glFmVCMwpJ5eVTR5rBJFsaGuaQinPrGfFcBE2c2SA2l701rf8RWglOr5vfOXlb8TcjumDMe4f4VGCM7c2tyZjgUxXcWfDnM94/h6MEvSkECHNxol/ibXK+SIi8boC8Wd5rqLLcnirZzx5rIgtmJ+xknraRRLjOc/66ALHVYOmsbvVTH0SSYdXz8f5pD1wMkEXyDWaWmb9wfHtS2Wr+fVX3rtVlqwRjZFPaLoX8NvkaTr3Pw7UjX5JRgGEWnMixepJT0nITO8B2YSyDOklVuCwb3rRoOvuBPGgTx5YUUff1kW6C8afjFg2cmfyrI+VZi/Sv5dbx2i7G4JZ2iBB7IMflKFamYlBFDx0/nZs/c/C2QpqWScjrvlOWuTtOTBfkWKPzr734qm7FYKXb4nCHRRSVQH9TwOS7Xm64NSEP70RxlCQK05//3hBdm5jHL7D/BFu56l/ByBMArRHyjoiQ0/TcAxctDpbYZuj7GkNsCAwEAAQ==

Sandbox integration flow

Our sandbox environment provides an easy way to test integrations and get familiar with the system’s UI, without performing real blockchain interactions or crediting funds in advance.

To get started, all you need is a sandbox organisation, which we will set up for you. Once this is done, the admin user will be able to invite other team members and explore the system flows through the dashboard. The process of testing any integration can also begin once the admin creates an API key.

All endpoints described in our documentation are also available in the sandbox environment using the correct URL and path. Multiple flows can be observed and tested by using the request parameters specified for each endpoint. However some endpoints might have limited capabilities when compared to their production counterparts.

Crypto deposits

For deposits the users can test the flows that result in a corresponding payments status( see statuses for payments and deposits) by passing a certain string keyword in the client label field.

For example to test a payment, that results in status DEPOSITED and has a single CONFIRMED deposit to it, the user should use client label like exact-01

The keyword should always be at the start of the client label.

Prefix	Payment status	Processing result
exact	DEPOSITED	One CONFIRMED deposit that matches the expected deposit currency, network and amount.
underpaid	DEPOSITED	One CONFIRMED deposit that matches the expected deposit currency and network. The actual deposit amount will be half of the expected amount.
overpaid	OVERPAID	One CONFIRMED deposit that matches the expected deposit currency and network. The actual deposit amount will be twice the expected amount. In addition, one OVERPAYMENT refund for half the actual amount.
follow-up	OVERPAID	Two CONFIRMED deposits that match the expected deposit currency, network and amount exactly. In addition, one FOLLOW_UP_DEPOSIT refund for half the actual amount.
below-minimum	UNPROCESSABLE	One UNPROCESSABLE deposit that matches the expected deposit currency and network. Tthe actual deposit amount is will be less than the minimum deposit amount.
blocked	BLOCKED	One BLOCKED deposit that matches the expected deposit currency, network and amount exactly. In addition, one refund for the entire actual amount.

A callback notification can be expected for deposits with status CONFIRMED.

Crypto withdrawals

For withdrawals you can test different statuses by triggering them with a prefix in the label of the withdrawal.

For example to test a crypto withdrawal that results in status SENT, the client label can be completed-withdrawal-01.

The keyword should always be at the start of the client label.

Prefix	Crypto withdrawal status
completed	SENT
failed	ABORTED
blocked	REJECTED