API Reference
  1. Transactions
  2. Transactions

Create a transaction

post
https://sandbox-api.coris.ai/api/v0_2/accounts//transactions/

Adds a transaction to an account, or updates it if the transaction_id already exists, so retries are safe. Use it to push payments from your own system so Coris can monitor them, or use Create a file upload to load many at once. Stripe and Adyen platforms do not need this call, because their transactions arrive through the connection.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

The account's Coris ID or your reference_id. Example: your_id_1.

Body Params

The transaction to add or update.

processor
object

The processor that handled this payment. If you send it, processor_id and processor_type are required, and a call without them returns 500.

string
required

Your ID for this transaction, up to 100 characters. Sending the same ID again updates the transaction.

integer

When the transaction happened, in epoch seconds or milliseconds.

string

The customer's email address on the transaction. Example: [email protected].

string

The email address in the billing details. Example: [email protected].

string

The customer's IP address, if available. Example: 203.0.113.42.

integer
required

The transaction amount, in the smallest currency unit, such as cents. Must not be zero.

string
Defaults to USD

The three-letter currency code.

string
enum

Which way the money moved. Default: Credit.

  • Credit: money in to the merchant.
  • Debit: money out of the merchant.
Allowed:
payer
object
required

Who paid, and how. payer.payment_method is required when you create a transaction.

string
enum
Defaults to Completed

The state of the transaction. On create, send Pending, Completed, Failed, Refunded or Disputed, in any case.

  • Pending: not yet final.
  • Completed: finished successfully. Sent on create only. Responses show Captured.
  • Failed: declined. Sent on create only. Responses show Declined.
  • Refunded: refunded.
  • Disputed: disputed.
  • Captured: response only. The funds were captured.
  • Authorized: response only. Authorized but not captured.
  • Declined: response only. The issuer or processor declined it.
  • Auth_Reversed: response only. The authorization was reversed.
  • Voided: response only. The transaction was voided.
  • Returned: response only. The payment was returned.
  • Unknown: response only. Coris could not map the source status.
boolean

true if the transaction has been disputed.

dispute_data
object

Dispute details, with amount and disputed_date. Without amount, the whole transaction counts as disputed.

boolean

true if the transaction has been refunded.

refunded_data
object

Refund details, with amount and refunded_date. Without amount, the whole transaction counts as refunded.

boolean

true if the transaction was declined.

string

Issuer authorization or decline response code, for example 59 for suspected fraud. Availability depends on the processor, and responses do not return it on transactions you push.

string

Card authorization code from the processor. Recommended, because it helps Coris match this payment to later records.

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

422

Invalid payment method details or verification checks. Card checks must use pass, fail, unavailable, or unchecked; raw card CVC/CVV/CID values are rejected.

Updated about 23 hours ago

Did this page help you?
Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
text/html

Updated about 23 hours ago

Did this page help you?