Skip to main content

Frequently Asked Questions

Find answers to common questions about integrating with Rails Services.

General Questions​

What is Rails Services?​

Rails Services is a comprehensive financial services platform that provides APIs for payment processing, digital asset management, and blockchain operations. Our microservices architecture enables PFIs, custodian banks, and technology partners to integrate modern financial services into their applications.

What types of organizations can integrate with Rails Services?​

  • Payment Financial Institutions (PFIs): Banks, credit unions, and financial service providers
  • Custodian Banks: Institutions providing custody and settlement services
  • Technology Partners: Fintech companies building financial solutions
  • Enterprise Clients: Large organizations requiring payment processing capabilities

Which currencies and regions are supported?​

Currently, we support:

  • Currencies: USD (primary), with EUR and GBP in development
  • Regions: United States (primary), with expansion to EU and UK planned
  • Regulatory Compliance: SOX, PCI DSS, AML/KYC requirements

Authentication & Security​

How do I obtain API credentials?​

  1. Complete the onboarding process with our sales team
  2. Provide required compliance documentation (KYC, business registration, etc.)
  3. Once approved, you'll receive sandbox credentials for testing
  4. Production credentials are provided after security review

How long are JWT tokens valid?​

  • Access tokens: 1 hour
  • Refresh tokens: 30 days
  • Tokens are automatically refreshed by our SDKs

What security measures should I implement?​

  • Store API keys securely (environment variables, key management systems)
  • Use HTTPS for all communications
  • Implement proper authentication flows
  • Enable IP allowlisting for production endpoints
  • Rotate API keys regularly

Can I use the same API key for multiple environments?​

No, API keys are environment-specific:

  • Sandbox keys only work in the sandbox environment
  • Production keys only work in the production environment
  • This prevents accidental production operations during testing

Integration Questions​

How long does integration typically take?​

Integration timelines vary by complexity:

  • Basic PFI integration: 2-4 weeks
  • Custodian integration: 4-6 weeks
  • Complex multi-service integration: 6-12 weeks

What programming languages are supported?​

We provide official SDKs for:

  • Node.js/JavaScript
  • Python
  • Java
  • C#

Community SDKs are available for PHP, Ruby, and Go.

Do I need to implement all services?​

No, you can integrate with specific services based on your needs:

  • Use only the Transaction Manager for payment processing
  • Integrate with the Blockchain Service for digital assets
  • Combine multiple services for comprehensive functionality

Can I test the integration before going live?​

Yes, we provide a comprehensive sandbox environment:

  • Identical to production APIs
  • Test data and scenarios
  • Event monitoring tools
  • No real money transactions

Transaction Processing​

What transaction types are supported?​

  • Deposits: Customer funds into the system
  • Withdrawals: Customer funds out of the system
  • Transfers: Between participants in the network
  • Digital Obligation Deposits: Blockchain-based transactions

What are the transaction limits?​

Limits vary by participant and are configured during onboarding:

  • Per transaction: Typically $1M for institutional clients
  • Daily limits: Customizable based on risk assessment
  • Monthly limits: Set according to business requirements

How long do transactions take to process?​

  • Deposits: 1-3 business days (depends on banking network)
  • Withdrawals: Same day to 1 business day
  • Transfers: Near real-time to same day
  • Blockchain transactions: 5-15 minutes for confirmation

Can transactions be cancelled?​

  • Pending transactions: Can be cancelled before processing
  • Processing transactions: Cannot be cancelled
  • Completed transactions: Cannot be cancelled, but reversal transactions can be initiated

What happens if a transaction fails?​

  • Failed transactions are automatically marked as FAILED
  • Funds are returned to the source account
  • Detailed error information is available via API
  • Support notifications are sent for technical failures

Compliance & AML​

What compliance requirements does Rails Services meet?​

  • SOX compliance: Financial reporting and data integrity
  • PCI DSS: Payment card data security
  • AML/KYC: Anti-money laundering and customer verification
  • Bank Secrecy Act: US financial monitoring requirements

Do I need to implement my own AML screening?​

Rails Services provides built-in AML screening:

  • Automatic transaction monitoring
  • Risk scoring algorithms
  • Sanctions list checking
  • Manual review workflows

You can also integrate your own AML providers if preferred.

What information is required for KYC?​

For individuals:

  • Full name and address
  • Date of birth
  • Government-issued ID
  • Social Security Number (US)

For businesses:

  • Business registration documents
  • Beneficial ownership information
  • Financial statements
  • Proof of address

How long does KYC approval take?​

  • Individual KYC: 1-2 business days
  • Business KYC: 3-5 business days
  • Complex cases: Up to 10 business days

Technical Questions​

What are the API rate limits?​

Rate limits depend on your service tier:

  • Standard: 1,000 requests/hour
  • Premium: 10,000 requests/hour
  • Enterprise: Custom limits

Rate limit headers are included in all responses.

How do I handle API errors?​

Implement proper error handling:

  • Check HTTP status codes
  • Parse error response JSON
  • Implement retry logic for retryable errors
  • Log errors for monitoring

See our Error Handling Guide for details.

Can I use Rails Services APIs from a mobile app?​

Yes, but follow security best practices:

  • Never embed API keys in mobile apps
  • Use a backend proxy for API calls
  • Implement proper authentication flows
  • Use certificate pinning for additional security

What monitoring and logging is available?​

  • Request logs: Available in your dashboard
  • Transaction history: Complete audit trail
  • Performance metrics: Response times and error rates

Billing & Pricing​

How is Rails Services priced?​

Pricing typically includes:

  • Monthly subscription fees
  • Per-transaction fees
  • Volume discounts for high-volume clients
  • Custom pricing for enterprise clients

Contact our sales team for specific pricing information.

Are there any setup fees?​

Setup fees may apply for:

  • Complex integrations requiring custom development
  • Priority onboarding and support
  • Dedicated infrastructure requirements

Can I change my pricing plan?​

Yes, you can upgrade or downgrade your plan:

  • Upgrades take effect immediately
  • Downgrades take effect at the next billing cycle
  • Some limitations may apply for downgrades

Support & Maintenance​

What support is available?​

  • Documentation: Comprehensive guides and API reference
  • Developer Support: Technical integration assistance
  • Email Support: Business inquiries and account management
  • Emergency Support: 24/7 for production issues (Enterprise tier)

What are the SLA commitments?​

  • API Availability: 99.9% uptime (99.99% for Enterprise)
  • Response Times: <200ms average API response time
  • Support Response: 4 hours for production issues
  • Planned Maintenance: Announced 48 hours in advance

How do I report a bug or request a feature?​

  • Bugs: Contact support with detailed reproduction steps
  • Feature Requests: Submit through your account dashboard
  • SDK Issues: Create GitHub issues in the respective SDK repository
  • Security Issues: Report security concerns

What happens during maintenance?​

  • Planned maintenance is announced in advance
  • APIs remain available during most maintenance windows
  • Critical security updates may require brief downtime
  • Status updates are posted on our status page

Migration & Upgrades​

How do I migrate from another payment processor?​

Our migration services include:

  • Data mapping: Convert existing transaction data
  • Parallel testing: Run both systems simultaneously
  • Gradual migration: Migrate customers in batches
  • Rollback procedures: Safety measures for issues

What happens when new API versions are released?​

  • Backward compatibility: Maintained for at least 12 months
  • Migration guides: Detailed documentation for changes
  • Deprecation notices: 6 months advance notice
  • SDK updates: Automatic compatibility with new versions

Can I rollback to a previous API version?​

Yes, within the supported compatibility window:

  • Change the version in your API requests
  • Update SDK versions if needed
  • Test thoroughly before production rollback

Data & Privacy​

Where is my data stored?​

  • Primary region: United States (AWS US-East)
  • Backup regions: US-West for disaster recovery
  • International: Data residency options for global clients
  • Encryption: All data encrypted at rest and in transit

What data retention policies apply?​

  • Transaction data: Retained for 7 years (regulatory requirement)
  • Log data: Retained for 12 months
  • Personal data: Retained according to applicable privacy laws
  • Backup data: Same retention as primary data

Is my data shared with third parties?​

We only share data when:

  • Required by law or regulation
  • Necessary for service operation (e.g., custodian banks)
  • With your explicit consent
  • For fraud prevention and security

How do I delete customer data?​

Submit data deletion requests through:

  • Your account dashboard
  • API endpoints for automated deletion
  • Support tickets for complex cases
  • Compliance with GDPR "right to be forgotten"

Troubleshooting​

My API calls are failing with 401 errors​

Check:

  • API key is correct and not expired
  • Using the right environment (sandbox vs production)
  • JWT token is valid and not expired
  • Headers are properly formatted

Transaction processing is slow​

Consider:

  • Banking network delays (normal for deposits)
  • AML review requirements (manual review needed)
  • Peak processing times (higher volume periods)
  • Network connectivity issues

Getting rate limit errors​

Solutions:

  • Implement exponential backoff
  • Optimize API usage patterns
  • Consider upgrading your tier
  • Use batch operations where available

Getting More Help​

Contact Information​

Additional Resources​

Can't find what you're looking for? Contact our support team for assistance with your Rails Services integration.