Update transaction metadata

post

https://sandbox-api.coris.ai/api/v0_2/transaction_metadata/

Adds or changes your own key-value metadata on one Stripe payment and returns 202 even if the payment has not arrived. Coris stores it for you to read back, and standard rules, alerts and the portal do not use it. For metadata on an account, use Update account metadata.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Responses

202

Coris accepted the metadata, and the body is empty. If the payment has not arrived, Coris holds the metadata and applies it on arrival. With no match within 3 days, Coris drops it.

A 202 does not confirm the payment. A mistyped ID, an unknown source_transaction_type or a body that is not a JSON object also returns 202, and nothing is stored. Confirm with Get transaction metadata once the payment has arrived.

You cannot list held metadata. To drop a held key, post it again with null: Coris applies held calls in order.

Language

Credentials

Header

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

text/html

application/json

400A query parameter or the body is missing. An empty object counts as missing. The body is a plain-text message, so read it and send source_transaction_type, source_transaction_id and at least one key-value pair.

401The key is missing, or it is wrong for this host. Send Authorization: Token YOUR_API_KEY with a key issued for this environment.

403A scoped key cannot use this route, and gets JSON with detail. Use a key without account limits.

429You passed a rate limit. If Retry-After is present, wait that many seconds, then retry. If it is absent, you hit the concurrency limit, so back off for a few seconds and reduce parallel calls.

500Coris could not complete the request. Retry with backoff. If it continues, contact support.