TicketUserServices

UpdateRecurringPaymentCardRequest

The following routes are available for this service:
POST	/recurringPayments/card
POST	/recurringPayments/{Id}/card


export class UpdateRecurringPaymentCardResult
{
    public ok?: boolean;
    public id?: number;
    public effect?: string;
    public priorStatus?: string;
    public status?: string;
    public resumed?: boolean;
    public nextPayment?: string;
    public statusCode?: number;
    public message?: string;

    public constructor(init?: Partial<UpdateRecurringPaymentCardResult>) { (Object as any).assign(this, init); }
}

export class UpdateRecurringPaymentCardRequest
{
    public id?: number;
    public paymentTokenId?: string;
    public phone?: string;
    public token?: string;
    public panLastFour?: string;
    public expYear?: string;
    public expMonth?: string;
    public via?: string;

    public constructor(init?: Partial<UpdateRecurringPaymentCardRequest>) { (Object as any).assign(this, init); }
}

TypeScript UpdateRecurringPaymentCardRequest DTOs

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 /recurringPayments/card HTTP/1.1 
Host: stubbur-app.azurewebsites.net 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	id: 0,
	paymentTokenId: String,
	phone: String,
	token: String,
	panLastFour: String,
	expYear: String,
	expMonth: String,
	via: String
}

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

{
	ok: False,
	id: 0,
	effect: String,
	priorStatus: String,
	status: String,
	resumed: False,
	nextPayment: 0001-01-01,
	statusCode: 0,
	message: String
}