Get Credit Payment

Credit Payment ID or UUID. For ID no prefix is used e.g. `e28zov4fw0v2`. For UUID use prefix `uuid-`, e.g. `uuid-123457890`.

The UUID is useful for matching data with the CSV exports and building URLs into Recurly's UI.

The action for which the credit was created.

One ofpaymentreductionrefundwrite_off

The unique identifier of the account.

The email address used for communicating with this customer.

Unique ID to identify a dunning campaign. Used to specify if a non-default dunning campaign should be assigned to this account. For sites without multiple dunning campaigns enabled, the default dunning campaign will always be used.

Unique ID to identify the business entity assigned to the invoice. Available when the `Multiple Business Entities` feature is enabled.

One ofchargecreditlegacy

One ofopenpendingprocessingpast_duepaidclosedfailedvoidedDefault "all"

Unique ID to identify the business entity assigned to the invoice. Available when the `Multiple Business Entities` feature is enabled.

One ofchargecreditlegacy

One ofopenpendingprocessingpast_duepaidclosedfailedvoidedDefault "all"

3-letter ISO 4217 currency code.

Total credit payment amount applied to the charge invoice.

For credit payments with action `refund`, this is the credit payment that was refunded.

The UUID is useful for matching data with the CSV exports and building URLs into Recurly's UI.

If this transaction is a refund (`type=refund`), this will be the ID of the original transaction on the invoice being refunded.

Must be sent for one-time transactions in order to provide context on which entity is submitting the transaction to ensure proper fraud checks are observed, such as 3DS. If the customer is in session, send `customer`. If this is a merchant initiated one-time transaction, send `merchant`.

One ofcustomermerchant

This conditional parameter is useful for merchants in specific industries who need to submit one-time Merchant Initiated transactions in specific cases. Not all gateways support these methods, but will support a generic one-time Merchant Initiated transaction. Only use this if the initiator value is "merchant". Otherwise, it will be ignored. - Incremental: Send `incremental` with an additional purchase if the original authorization amount is not sufficient to cover the costs of your service or product. For example, if the customer adds goods or services or there are additional expenses. - No Show: Send `no_show` if you charge customers a fee due to an agreed-upon cancellation policy in your industry. - Resubmission: Send `resubmission` if you need to attempt collection on a declined transaction. You may also use the force collection behavior which has the same effect. - Service Extension: Send `service_extension` if you are in a service industry and the customer has increased/extended their service in some way. For example: adding a day onto a car rental agreement. - Split Shipment: Send `split_shipment` if you sell physical product and need to split up a shipment into multiple transactions when the customer is no longer in session. - Top Up: Send `top_up` if you process one-time transactions based on a pre-arranged agreement with your customer where there is a pre-arranged account balance that needs maintaining. For example, if the customer has agreed to maintain an account balance of 30.00 and their current balance is 20.00, the MIT amount would be at least 10.00 to meet that 30.00 threshold.

One ofincrementalno_showresubmissionservice_extensionsplit_shipmenttop_upDefault "none"

If the transaction is charging or refunding for one or more subscriptions, these are their IDs.

- `authorization` – verifies billing information and places a hold on money in the customer's account. - `capture` – captures funds held by an authorization and completes a purchase. - `purchase` – combines the authorization and capture in one transaction. - `refund` – returns all or a portion of the money collected in a previous transaction to the customer. - `verify` – a $0 or $1 transaction used to verify billing information which is immediately voided.

One ofauthorizationcapturepurchaserefundverify

Describes how the transaction was triggered.

One ofapichargebackexternal_recoveryforce_collecthppmerchantrecurly_adminrecurlyjsrecurringrefunded_externallytransparenttoken_apiapi_force_collectapi_sub_changeapi_verify_cardrefund_balanceamazon_v2_ipn

3-letter ISO 4217 currency code.

The description that gets sent to the gateway.

Total transaction amount sent to the payment gateway.

The current transaction status. Note that the status may change, e.g. a `pending` transaction may become `declined` or `success` may later become `void`.

One ofchargebackdeclinederrorpendingprocessingscheduledsuccessvoid

Did this transaction complete successfully?

Indicates if the transaction was completed using a backup payment

Indicates if part or all of this transaction was refunded.

The method by which the payment was collected.

One ofautomaticmanual

IP address provided when the billing information was collected: - When the customer enters billing information into the Recurly.js or Hosted Payment Pages, Recurly records the IP address. - When the merchant enters billing information using the API, the merchant may provide an IP address. - When the merchant enters billing information using the UI, no IP address is recorded.

For declined (`success=false`) transactions, the message displayed to the merchant.

For declined (`success=false`) transactions, the message displayed to the customer.

Transaction message from the payment gateway.

Transaction reference number from the payment gateway.

Time, in seconds, for gateway to process the transaction.

The values in this field will vary from gateway to gateway.

When processed, result from checking the CVV/CVC value on the transaction.

One ofDIMNPSUX

When processed, result from checking the overall AVS on the transaction.

One ofABCDEFGHIJKLMNOPQRSTUVWXYZ