| PUT,OPTIONS | /portal/{Token}/payment |
|---|
"use strict";
export class PortalRecordPaymentResponse {
/** @param {{ResponseStatus?:ResponseStatus,Success?:boolean,Paid?:boolean,ReceiptUrl?:string,Message?:string}} [init] */
constructor(init) { Object.assign(this, init) }
/** @type {ResponseStatus} */
ResponseStatus;
/** @type {boolean} */
Success;
/** @type {boolean} */
Paid;
/** @type {string} */
ReceiptUrl;
/** @type {string} */
Message;
}
export class PortalRecordPaymentRequest {
/** @param {{Token?:string,StripeToken?:string}} [init] */
constructor(init) { Object.assign(this, init) }
/** @type {string} */
Token;
/** @type {string} */
StripeToken;
}
JavaScript PortalRecordPaymentRequest DTOs
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
PUT /portal/{Token}/payment HTTP/1.1
Host: api.dev.dynamics.trendsic.com
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
Token: String,
StripeToken: String
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
ResponseStatus:
{
ErrorCode: String,
Message: String,
StackTrace: String,
Errors:
[
{
ErrorCode: String,
FieldName: String,
Message: String,
Meta:
{
String: String
}
}
],
Meta:
{
String: String
}
},
Success: False,
Paid: False,
ReceiptUrl: String,
Message: String
}