Jump to Content
Push-to-Card Gateway
Guides
Push-to-Card Gateway
Guides

Cross River Payment Solutions

  • Push-to-Card Gateway
  • Card payment APIs
    • Authentication and authorization
    • Card authorization
    • Sending API requests and receiving responses
  • Card issuer response codes
  • HTTP response codes
  • Error codes
  • Terminology
  • Tutorial: Originate a Push to Card transaction
  • Tutorial: Originate an Account Funding Transaction (AFT)
  • Tutorial: Setting up your iframe to integrate with P2C

Push-to-Card gateway

  • Card Registration
    • Add a card
    • Get card details by card token
    • Get card information
    • Activate and Deactivate cards
  • iframes
    • Add iframes to your site
  • Transactions
    • Send funds to a payee
    • Request funds from a payor
    • Get push transactions
    • Get transaction details by card token and transaction ID (deprecated)
    • Get pull transactions
    • Get push transaction details by transaction ID
    • Get pull transaction details by transaction ID
  • Batch transactions
    • Send a batch transaction
    • Get batched transaction count status
    • Get a batched transaction by ID and transaction batch status
  • Webhooks
    • Register for webhook events
    • View registered webhook events
    • Update webhook registrations
    • Get webhooks by ID
    • Delete webhook events

HTTP response codes

Suggest Edits

The OFAC list API uses standard HTTP response codes to communicate the result of a request.

HTTP codeDescription
200Success
400General bad request response, some fields do not comply with the restrictions as mentioned in the documentation.
401Authentication error – if it’s expired or not valid.
500Technical difficulties at Cross River.

Updated 3 months ago