Create Transaction

Visit the About Transactions to learn more about Transaction methods, types, and requests parameters.

Response Codes
102 - Idempotent matched request currently processing
201 - Created, will include a Location response header
200 - Request Succeeded, but entity not created
400 - Bad Request, missing or invalid parameters
409 - Idempotent matched request already processed
422 - Request not process due to business constraints

📘

ACH & RTP Transaction Requests

The initial status from the ACH & RTP transaction request will be PROCESSING.

• ACH
  • The initial PROCESSING status depends on the banking partner processing the ACH funds movement. Our team will discuss the status differences during the integration/onboarding process.
  • ACH transactions can be processed "same day" (business day) or the "standard" 3-5 days. The PAID or FAILED status update will trigger a webhook once the final status is known.
• RTP
  • The roundtrip RTP request could take up to 30 seconds. A webhook will be sent when a definitive status is known.

📘

Card Transaction Requests - Instant Deposit and Instant Funding

Visa and Mastercard networks handle requests with expired cards differently.

• Visa will accept an expiration date in the past and attempt to process the transaction through the issuing bank. The bank will determine whether or not to honor the transaction. A Visa decline may result in action code 54.
• Mastercard will reject the transaction request. For this reason, we will validate the card expiration date before processing through Mastercard. If the card is expired, a 422 status code with ERR_CARD_ACCOUNT_EXPIRED will be returned in the API response.

❗️

Transaction ID with Error Response

The transaction_id parameter will not always be present in the error response body. Under certain 400 and 422 scenarios, the response is returned before processing of the transaction occurs.