recurly-client-0.1.0.0: Client for Recurly subscription management
Safe HaskellSafe-Inferred
LanguageHaskell2010

RecurlyClient.Operations.Update_a_billing_info

Description

Contains the different functions to run the operation update_a_billing_info

Synopsis

Documentation

update_a_billing_info Source #

Arguments

:: forall m. MonadHTTP m 
=> Update_a_billing_infoParameters

Contains all available parameters of this operation (query and path parameters)

-> BillingInfoCreate

The request body to send

-> ClientT m (Response Update_a_billing_infoResponse)

Monadic computation which returns the result of the operation

PUT /accounts/{account_id}/billing_infos/{billing_info_id}

If you're using Recurly.js to securely submit data from webforms without sending it through your server, you can associate the billing information with an account by passing in the `token_id`. The only other fields permitted with `token_id` are `primary_payment_method` and/or `backup_payment_method`.

For credit card payments you'll need the following required fields:

  • first_name
  • last_name
  • number
  • month
  • year

For external (not Recurly.js) tokenized payments you'll need the following required fields:

  • first_name
  • last_name
  • gateway_token
  • gateway_code

data Update_a_billing_infoParameters Source #

Defines the object schema located at paths./accounts/{account_id}/billing_infos/{billing_info_id}.PUT.parameters in the specification.

Constructors

Update_a_billing_infoParameters 

Fields

data Update_a_billing_infoResponse Source #

Represents a response of the operation update_a_billing_info.

The response constructor is chosen by the status code of the response. If no case matches (no specific case for the response code, no range case, no default case), Update_a_billing_infoResponseError is used.

Constructors

Update_a_billing_infoResponseError String

Means either no matching case available or a parse error

Update_a_billing_infoResponse200 BillingInfo

Updated billing information.

Update_a_billing_infoResponse400 Error

Bad request, perhaps invalid JSON?

Update_a_billing_infoResponse404 Error

Incorrect site or account ID.

Update_a_billing_infoResponse422 ErrorMayHaveTransaction

Invalid billing information, or error running the verification transaction.

update_a_billing_infoWithConfiguration Source #

Arguments

:: forall m. MonadHTTP m 
=> Configuration

The configuration to use in the request

-> Update_a_billing_infoParameters

Contains all available parameters of this operation (query and path parameters)

-> BillingInfoCreate

The request body to send

-> m (Response Update_a_billing_infoResponse)

Monadic computation which returns the result of the operation

PUT /accounts/{account_id}/billing_infos/{billing_info_id}

The same as update_a_billing_info but accepts an explicit configuration.

update_a_billing_infoRaw Source #

Arguments

:: forall m. MonadHTTP m 
=> Update_a_billing_infoParameters

Contains all available parameters of this operation (query and path parameters)

-> BillingInfoCreate

The request body to send

-> ClientT m (Response ByteString)

Monadic computation which returns the result of the operation

PUT /accounts/{account_id}/billing_infos/{billing_info_id}

The same as update_a_billing_info but returns the raw ByteString.

update_a_billing_infoWithConfigurationRaw Source #

Arguments

:: forall m. MonadHTTP m 
=> Configuration

The configuration to use in the request

-> Update_a_billing_infoParameters

Contains all available parameters of this operation (query and path parameters)

-> BillingInfoCreate

The request body to send

-> m (Response ByteString)

Monadic computation which returns the result of the operation

PUT /accounts/{account_id}/billing_infos/{billing_info_id}

The same as update_a_billing_info but accepts an explicit configuration and returns the raw ByteString.