📖
Inyo Developer Portal
  • API REFERENCES
    • Payments Gateway v2
      • Getting started
      • Background
        • System architecture
        • Gateway environment settings
      • Authentication Methods
      • Environments
      • Technical Resources
      • Mitigating Fraud
      • APIs
        • Tokenizing cards
        • Payment
          • Pull Transaction
            • Handling AVS / CVC
            • Handling 3D secure
          • Push Transaction
          • Pull and push in one step
          • Capture
          • Refund
          • Void
          • Get a payment
          • Get a list
        • Webhooks
        • Domain tables
          • Response Code
          • Payment Status
        • Test data
          • Cards
    • Remittances
      • Getting Started
      • Authentication
      • Data Population
        • Country
        • State
        • Banks
        • Payers
        • Settlement Rates
      • Sender
        • Sender Object
        • Register a Sender
        • User Agreement
        • Get Sender by ID
        • Sender Verification
          • ID Documents
            • Expired ID Documents
          • KYC Status
          • KYC Using Widget
          • KYC Using API
            • Get KYC fields
            • Update KYC Information
            • Initiate KYC
            • Get KYC Information
          • Sender Tier Upgrade
        • Sender ID Information
      • Funding Account
        • Add Funding Account
          • OAuth Integration
        • Funding Account Object
        • Get Funding Account
        • Delete Funding Account
      • Recipient
        • Recipient Object
        • Add a Recipient
        • Get Recipient Details
        • Update Recipient
        • Recipient Document
      • Recipient Account
        • Recipient Account Object
        • Add a Recipient Account
        • Get Recipient Account
        • Get Account Information
      • Transaction
        • Transaction Object
        • Get Transaction Limits
        • Create a Transaction
          • 3DS Verification
          • Bonus/Discount
        • Get Transaction Details
        • Cancel Transaction
        • Delivery Request
        • Self-Payout
        • Transaction Invoice
      • Webhooks
        • Subscriptions
          • Subscribe
          • List Subscriptions
          • Pause Subscriptions
          • Remove Subscription
        • Integration
        • Events
      • Widget
        • Widget v1.0
          • Widget v1.0 Types
        • Widget v2.0
      • SANDBOX
        • Test Values
          • Geo-Fencing
          • Sender Verification
          • Funding Account
          • Transaction
  • USE CASE
    • Remittance
Powered by GitBook
On this page
  1. API REFERENCES
  2. Remittances

Authentication

PreviousGetting StartedNextData Population

Last updated 7 months ago

Inyo uses API keys to allow access to our APIs. Our servers are restricted by firewall rules and can only be accessed once credentials are generated.

Depending on the type of product being used, Inyo's team will provide a set of different keys: CLIENT_ID and CLIENT_SECRET.

For the Payout product, you must use X-Client-Id and X-Client-Secret in every API request header.

CLIENT_ID and CLIENT_SECRET values should never be used or shared publicly and should be stored properly in an encrypted format.

X-Client-Id: CLIENT_ID X-Client-Secret: CLIENT_SECRET

You will have to use the following URL to access our sandbox: https://api.sandbox.raas.hubcrossborder.com/v2

Use our Postman collection to quickly run through our API endpoint

For the Standalone Payment Gateway product, you must follow the OAuth protocol, by using the client_id and client_secret to generate an access token. The sandbox url is: https://sandbox-gw.simpleps.com/

More details about authentication, and testing data can be found in the API Reference, section.

Payment Gateway (standalone)