TicketUserServices

BorgunTest3DFinishProcessRequest

**Requires Authentication**
Requires the role:	Admin	Requires the permission:	ReadData

The following routes are available for this service:
POST	/borgunTest3D/Finish3DProcess	Test 3D

**BorgunTest3DFinishProcessRequest** Parameters:
Name	Parameter	Data Type	Required
Request	body	Borgun3DFinalRequest	No
ForcedPath	body	string	No
ForcedJSONRequest	body	string	No
SkipBorgunCall	body	bool?	No

**Borgun3DFinalRequest** Parameters:
Name	Parameter	Data Type	Required
TransactionType	form	string	No
Amount	form	int	No
Currency	form	string	No
TransactionDate	form	DateTime?	No
OrderId	form	string	No
PaymentMethod	form	Borgun3DFinalPaymentMethodInfo	No
ThreeDSecure	form	Borgun3DFinal3DSecureInfo	No

**Borgun3DFinalPaymentMethodInfo** Parameters:
Name	Parameter	Data Type	Required	Description
PaymentType	form	string	No
Token	form	string	No

**Borgun3DFinal3DSecureInfo** Parameters:
Name	Parameter	Data Type	Required	Description
DataType	form	string	No
MpiToken	form	string	No

**BorgunTest3DFinishProcessResponse** Parameters:
Name	Parameter	Data Type	Required
Response	form	BorgunFinal3DResponse	No
StatusCode	form	int	No
Message	form	string	No
ForcedPath	form	string	No
ForcedJSONRequest	form	string	No
JSONRequest	form	string	No
JSONResponse	form	string	No
RequestPath	form	string	No
RequestSent	form	string	No
RequestReceived	form	string	No

**BorgunFinal3DResponse** Parameters:
Name	Parameter	Data Type	Required
TransactionId	form	string	No
TransactionType	form	string	No
Amount	form	int	No
Currency	form	string	No
TransactionDate	form	DateTime	No
OorderId	form	string	No
AuthCode	form	string	No
ActionCode	form	string	No
TransactionStatus	form	string	No
PaymentMethod	form	BorgunPaymentMethodInfo	No
ThreeDSecure	form	Borgun3DSecureInfo	No
LifeCycleId	form	string	No

**BorgunPaymentMethodInfo** Parameters:
Name	Parameter	Data Type	Required
PaymentType	form	string	No
PAN	form	string	No
Token	form	string	No
CardType	form	string	No
IsDebit	form	string	No

**Borgun3DSecureInfo** Parameters:
Name	Parameter	Data Type	Required	Description
SecurityLevelInd	form	string	No
Xid	form	string	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv

HTTP + JSV

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /borgunTest3D/Finish3DProcess HTTP/1.1 
Host: stubbur-autoupdates-live.smartnewapis.com 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	request: 
	{
		transactionType: String,
		amount: 0,
		currency: String,
		transactionDate: 0001-01-01,
		orderId: String,
		paymentMethod: 
		{
			paymentType: String,
			token: String
		},
		threeDSecure: 
		{
			dataType: String,
			mpiToken: String
		}
	},
	forcedPath: String,
	forcedJSONRequest: String,
	skipBorgunCall: False
}

HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length

{
	response: 
	{
		transactionId: String,
		transactionType: String,
		amount: 0,
		currency: String,
		transactionDate: 0001-01-01,
		oorderId: String,
		authCode: String,
		actionCode: String,
		transactionStatus: String,
		paymentMethod: 
		{
			paymentType: String,
			pan: String,
			token: String,
			cardType: String,
			isDebit: String
		},
		threeDSecure: 
		{
			securityLevelInd: String,
			xid: String
		},
		lifeCycleId: String
	},
	statusCode: 0,
	message: String,
	forcedPath: String,
	forcedJSONRequest: String,
	jsonRequest: String,
	jsonResponse: String,
	requestPath: String,
	requestSent: String,
	requestReceived: String
}