Simulate card management

in this tutorial, you'll learn how to ✅ simulate these card management actions clearing reversal incremental transaction single message clearing single message reversal if you are new to card issuing we recommend you read the cards concept pages before starting this tutorial the tutorial assumes you have a knowledge of apis and how they work for more information on sending api calls, see structure the tutorial uses these api endpoints true false 293false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type before you begin make sure you have quickstart client id register relevant webhook events to receive the webhook events for this tutorial both partner accounts need to accounts, cards and payment events each specific webhook event type once you are registered, the event objects are sent to the registered urls the event object contains a list of resource identifiers used to download details on each event simulate card management the simulate endpoints within card management allow you to simulate most of the transaction scenarios you would experience in a live environment to simulate authorization call simulate card authorization this endpoint simulates a merchant authorization that affects the available balance on the deposit account simulate authorization request curl location 'https //sandbox crbcos com/cardmanagement/v1/simulate/authorization' \\ \ data '{ "amount" 1999, "cardid" "8c6a53e0 83ad 4b76 b446 b300006a3e6a", "merchantcountrycode" "us", "merchantname" "streamflix", "merchantstreet" "123 any st", "merchantcity" "anywhere", "merchantstate" "ny", "merchantpostalcode" "10001", "cardnetwork" "visa", "additionalamounts" \[], "processingcode" "billpayment" }' the response includes the retrievalreferencenumber and the cardid you need these values to replace the memo post with a core transaction to post the activity record to the account, using the endpoint post /v1/simulate/clearing as explained below simulate authorization response { "retrievalreferencenumber" "644371423186", "cardid" "8c6a53e0 83ad 4b76 b446 b300006a3e6a" } to simulate clearing in a real transaction, when the authorization request is made, a memo post reflects the account and impacts the available balance however, the memo post remains until the clearing endpoint is called calling the simulate card clearing endpoint replaces the memo post with a core transaction to post the activity record to the account in this simulation, authorization is not complete and the transaction does not post on the account until the simulate/clearing endpoint is called using the retrievalreferencenumber and cardid simulate clearing request curl location 'https //sandbox crbcos com/cardmanagement/v1/simulate/clearing' \\ \ data '{ "cardid" "8c6a53e0 83ad 4b76 b446 b300006a3e6a", "retrievalreferencenumber" "644371423186", "processingcode" "billpayment" }' to simulate reversal this endpoint is used to reverse an existing authorization using the retrievalreferencenumber returned in the response to the simulate card reversal endpoint this reverses the original authorization placed on the account and removes it from the deposit account activity the amount in this request can be any value and does not have to be the same amount as the original clearing transaction, which allows for a partial amount reversal simulate reversal request curl location 'https //sandbox crbcos com/cardmanagement/v1/simulate/reversal' \\ \ data '{ "cardid" "8c6a53e0 83ad 4b76 b446 b300006a3e6a", "retrievalreferencenumber" "654492282074", "amount" "123" }' to simulate a incremental transaction this endpoint, used with the retrievalreferencenumber returned by the simulate card incremental endpoint, creates an incremental transaction reflected in the deposit account activity an example of an incremental transaction is when a hotel adds an additional charge for an item charged to your room simulate incremental request curl location 'https //sandbox crbcos com/cardmanagement/v1/simulate/incremental' \\ \ data '{ "cardid" "8c6a53e0 83ad 4b76 b446 b300006a3e6a", "retrievalreferencenumber" "654492282074", "amount" "123" }' to simulate single message clearing a single message is a message type that uses real time verification and requires the cardholder to enter their pin to authorize and clear their transaction an example of a transaction that uses the simulate single message clearing enpoint is an atm withdrawal simulate single message clearing request curl location 'https //sandbox crbcos com/cardmanagement/v1/simulate/single message clearing' \\ \ data '{ "processingcode" "purchase", "cardid" "8c6a53e0 83ad 4b76 b446 b300006a3e6a", "amount" "22", "merchantcountrycode" "us", "merchantname" "streamflix", "merchantstreet" "123 any st", "merchantcity" "anywhere", "merchantstate" "ny", "merchantpostalcode" "10001", "cardnetwork" "visa", "additionalamounts" \[ { "amounttype" "unknown", "accounttype" "notspecified", "amount" "10" } ] } ' to simulate single message reversal this endpoint allows you to create a reversal transaction to a single message clearing transaction for example, use the simulate single message reversal endpoint to simulate a purchase and then simulate a return with the single message reversal simulate single message reversal request curl location 'https //sandbox crbcos com/cardmanagement/v1/simulate/single message reversal' \\ \ data '{ "amount" "22", "processingcode" "purchase", "cardid" "8c6a53e0 83ad 4b76 b446 b300006a3e6a", "merchantcountrycode" "us", "merchantname" "streamflix", "merchantstreet" "123 any st", "merchantcity" "anywhere", "merchantstate" "ny", "merchantpostalcode" "10001", "cardnetwork" "visa", "additionalamounts" \[ { "amounttype" "unknown", "accounttype" "notspecified", "amount" "10" } ] } '