Jump to Content
P2C Disbursements
Guides
P2C Disbursements
Guides

Cross River Payment Solutions

  • Cross River payment solutions
  • Card payment APIs
    • Authentication
    • P2C card authorization
    • HTTP request headers
    • Verifying a token
  • Response codes
  • Error codes
  • Terminology
  • Status Page

P2C Disbursements

  • Card Registration
    • Add a card
    • Get card details by card token
    • Get card information
    • Activate and Deactivate cards
    • Card Registration Reference
  • Transactions
    • Push funds
    • Pull funds
    • 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
    • Push Transaction Reference
    • Pull Transaction Reference
  • iframes
    • Sign up a card via an iframe
  • Batch transactions
    • Send a batch transaction
    • Get batched transaction count status
    • Get a batched transaction by ID and transaction batch status
    • Batch Transaction Reference
  • Webhooks
    • P2C Webhooks
    • Register for webhook events
    • View registered webhook events
    • Delete webhook events
    • Update webhook registrations
    • Get webhooks by ID
    • Webhook Reference

Beka Payments Monitor API

  • Beka Payments Monitor APIs
  • The payment object
  • Send a list of payments
  • Get a list of payment information by ID
  • Send your total payment details for the last hour
  • Get total payment information

Beka Payments Monitor APIs

Suggest Edits

Beka APIs allow merchants that have a reserved account at CRB to send transaction updates.

Updated about 1 month ago


Did this page help you?