Loading...
Use this endpoint to create a card present auth transaction against a credit card.
AuthTokenV2 which must be sent with each request. Please refer to the [AuthTokenV2](/referral-partner/api/definitions/authentication#authtokenv2) documentation for details.
Indicates the type of data that you are sending in your request.
Your unique Partner REST API key for server-side requests. Note - If you have not received your API key, contact our [Integration Services](/referral-partner/support/integration-support) team.
GUID that you must generate for each request. The value for this parameter should have a prefix of MER-, for example MER-GUID. For Tokenization calls use a prefix of API- or PFC-. Note: If you do not send a value for this parameter, we generate a value with a prefix of API- and return it in the header of the response.
API version in YYYY-MM-DD format.
Name of the application.
Version of your application.
Device details to be used for payment in a format like 'Namespace:DeviceID', where namespace refers to target system information. For Genius terminals use 'cedevice' as namespace and for Edge express use 'rcm', example 'cedevice::aear4i'.
Reference ID for transaction. This can be a merchant-generated unique identifier for the transaction. The reference_id in the request will be echoed back in the transaction response. This reference_id can also be used for follow-on transactions. If reference_id is not passed with the request, one will be generated by the payment gateway and returned in the response. String type:AlphaNumeric.
Payment object in request payload for primary card present sales transactions.
Receipt object in request payload to create a sales, authorizations, or independent returns transaction, or to create a returns associated with a sales transaction.
Transaction object in request payload to create a card present sales transaction.