Each IP address is subject to the following rate limits:

• Maximum 40 requests per second
• Maximum 5,000 requests per 15 minutes

Production Environment

• 47.88.34.101
• 47.88.103.100
• 47.88.61.14
• 47.89.250.82
• 47.89.240.147
• 47.88.57.67

Sandbox Environment

• 120.25.101.116
• 47.254.89.98
• 47.89.240.147

Please provide as much of the following information as possible:

• Issue description
• Environment (Production or Sandbox)
• Request URL
• Request body and response body
• cURL request (if available)

Each sub-account is limited to 2 KYC submission attempts within a 24-hour period.
If the maximum number of failed attempts is reached, further submissions will be rejected.

Please do not resubmit immediately. Check the KYC status and rejection reason first, and retry after 24 hours.

This is a compliance requirement. The allowed KYC age range is 18–65 years old.

To ensure data consistency and global compliance, all phone number fields in Cardholder and KYC-related APIs are validated and parsed using Google’s official libphonenumber library (https://github.com/google/libphonenumber). Please use it to check if the phone number is valid.

The submitted phone number (countryCode + phoneNumber) is validated according to the library's rules, including but not limited to:

• Validity of the country / region calling code
• Correct phone number format
• Whether it can be parsed as a valid international phone number

Please ensure the phone number complies with the library's rules.

Please confirm:

• The applicant's country or region supports the selected document type
• The document has been uploaded correctly

Facial recognition failed during the liveness check. Please retry the identity verification process.

The name provided by the customer does not match the name shown on their identity document.
Please review and correct the submitted information.

The KYC request was rejected because the applicant uploaded an expired identity document.

Example error when submitting KYC:
Unsupported countries: RU

KYC is currently not supported for the following countries or regions:

• KP – North Korea (Democratic People's Republic of Korea)
• IR – Iran
• SY – Syria
• CU – Cuba
• SD – Sudan
• SS – South Sudan
• BY – Belarus
• LY – Libya
• RU – Russia (Russian Federation)
• VE – Venezuela
• MM – Myanmar (Burma)
• CR – Costa Rica
• CF – Central African Republic
• SO – Somalia
• UA – Ukraine

1.Applicant Selfie Requirements

✔️ Applicant Selfie Guidelines:

• The selfie must be taken by the actual applicant and match the submitted document
• The face must be clearly visible on the screen
• It is recommended to take the selfie in an area with sufficient lighting
• Avoid being too close or too far from the camera

❌ Common Selfie Issues:

• AI-generated, post-edited, composited, or filtered images
• Third-party photos (photos taken by another person)
• Wearing masks or hats
• Glasses are not recommended if avoidable

2.Identity Document Requirements

✔️ Document Photo Guidelines:

• The photo must show a complete and recognizable valid identification document
• Use a clear, straight-on photo (not angled or blurry)

❌ Document Photo Issues:

• Do not submit photos of printed copies (re-photographed)
• Do not submit screenshots
• Do not cover, mark or obscure any part of the document

This feature is currently supported only for Interlace Own HK Visa BINs.

If configuration is required, please contact Interlace technical support team.

Reference documentation:
Real-time Transaction Authorization Decision Interface Documentation

Please refer to the Velocity Control API documentation.

For prepaid cards, any remaining balance will be transferred to the Infinity Account.

If a refund occurs after the card has been deleted, the refunded amount will be credited to the Infinity Account on a T+1 basis.

For budget cards, refunds after deletion will be credited back to the original budget.

Cards with transactions in pending status cannot be deleted.

Cards that remain frozen for more than 30 days will be automatically deleted.
Deleted cards cannot be recovered. Please unfreeze the card promptly if you wish to continue using it.

Yes.
On the first day of each month, the system checks all card expiration dates and automatically deletes expired cards.

Before activating a physical card, the card must first complete the mailing (shipping) process. (Bulk ship physical cards)

Please ensure the physical card has been successfully created and shipped (including bulk shipment scenarios).

Please follow the steps below to create a card:

1. Retrieve all available card BINs under your account (List all available card BINs)

2. Create a cardholder using a binId from step 1 (Create a cardholder)

3. Retrieve available card binId from cardholder (Get a cardholder)

4. Get the binId from the results of step 1 and step 3

5. Create a prepaid or budget card using the matched binId

This error occurs when the binId used during card creation does not match the cardholder's assigned channel.

Transfers within the same accountId are supported as follows:

Supported:

• Infinity Account USD balance → CryptoConnect Wallet USD balance
• CryptoConnect Wallet balance (USD / USDC / USDT / WUSD) → Infinity Account USD balance

Not Supported:

• Infinity Account USD balance → CryptoConnect Wallet balance (USDC / USDT / WUSD)

Transfers between different accountIds within the same master account (Gateway mode only):

Supported (same currency only, e.g. USD → USD, USDC → USDC)

• Master merchant Infinity Account (USD balance) ↔ Sub-merchant Infinity Account (USD balance)
• Master merchant CryptoConnect Wallet ↔ Sub-merchant CryptoConnect Wallet
• Sub-merchant Infinity Account (USD balance) ↔ Sub-merchant Infinity Account (USD balance)
• Sub-merchant CryptoConnect Wallet ↔ Sub-merchant CryptoConnect Wallet

Not Supported:

• Cross-currency transfers (e.g. USD → USDC) ❌
• Transfers between different master merchants ❌

Collects funds from sub-wallets into the master wallet. This feature is available only in the MoR mode.