Transactions
Use the card token to call APIs
After signing the card up in P2C, the card token provided in the response is how you should identify the debit card in your API calls. The card token is the identifier you use between your system and Cross River.
Below are the endpoints available for transactions. Use these APIs to send funds (push) and receive funds (pull), and get transaction information and updates.
| Endpoint | Description |
|---|---|
| PUSH POST /api/transaction | This call sends a transaction request to transfer funds to a payee. |
| PULL POST /api/PullTransaction | This call sends a transaction request to transfer funds from a payee. |
| PUSH GET /api/transaction/{transactionId} | This call returns individual push transactions by the transaction ID. This is useful for validating a transaction or interacting with your GUI after returning the transaction list, if you do not have the card token. |
| PULL GET /api/PullTransaction/{transactionId} | This call returns individual pull transactions by the transaction ID. This is useful for validating a transaction or interacting with your GUI after returning the transaction list, if you do not have the card token. |
| GET /api/transaction/{cardToken}/{transactionId} | This call returns individual transactions by the card token ID and the transaction ID. This is useful for validating a transaction by card token ID. |
| PUSH GET /api/transaction | This call returns transactions. You can narrow down the returns by using the query parameters. |
| PULL GET /api/PullTransaction | This call returns transactions. You can narrow down the returns by using the query parameters. |
Updated 8 months ago