Card Payments group together interactions related to a single card payment, such as an authorization and its corresponding settlement.
The identifier for the Account the Transaction belongs to.
The Card identifier for this payment.
The ISO 8601 time at which the Card Payment was created.
The Digital Wallet Token identifier for this payment.
The interactions related to this card payment.
The Card Payment identifier.
The Physical Card identifier for this payment.
The summarized state of this card payment.
A constant representing the object's type. For this resource it will always be card_payment
.
Return the page of entries after this one.
Limit the size of the list that is returned. The default (and maximum) is 100 objects.
Filter Card Payments to ones belonging to the specified Account.
Filter Card Payments to ones belonging to the specified Card.
Return results after this ISO 8601 timestamp.
Return results before this ISO 8601 timestamp.
Return results on or after this ISO 8601 timestamp.
Return results on or before this ISO 8601 timestamp.
The identifier of the Card Payment.
Simulates expiring a Card Authorization immediately.
The identifier of the Card Payment to expire.
Simulates a purchase authorization on a Card. Depending on the balance available to the card and the amount
submitted, the authorization activity will result in a Pending Transaction of type card_authorization
or a Declined Transaction of type card_decline
. You can pass either a Card id or a Digital Wallet Token id to simulate the two different ways purchases can be made.
The authorization amount in cents.
The identifier of a Card Payment with a card_authentication
if you want to simulate an authenticated authorization.
The identifier of the Card to be authorized.
Forces a card decline with a specific reason. No real time decision will be sent.
The identifier of the Digital Wallet Token to be authorized.
The identifier of the Event Subscription to use. If provided, will override the default real time event subscription. Because you can only create one real time decision event subscription, you can use this field to route events to any specified event subscription for testing purposes.
The merchant identifier (commonly abbreviated as MID) of the merchant the card is transacting with.
The Merchant Category Code (commonly abbreviated as MCC) of the merchant the card is transacting with.
The city the merchant resides in.
The country the merchant resides in.
The merchant descriptor of the merchant the card is transacting with.
The state the merchant resides in.
Fields specific to a given card network.
The risk score generated by the card network. For Visa this is the Visa Advanced Authorization risk score, from 0 to 99, where 99 is the riskiest.
The identifier of the Physical Card to be authorized.
Fields specific to a specific type of authorization, such as Automatic Fuel Dispensers, Refund Authorizations, or Cash Disbursements.
The terminal identifier (commonly abbreviated as TID) of the terminal the card is transacting with.
Simulates the fuel confirmation of an authorization by a card acquirer. This happens asynchronously right after a fuel pump transaction is completed. A fuel confirmation can only happen once per authorization.
The amount of the fuel_confirmation in minor units in the card authorization's currency.
The identifier of the Card Payment to create a fuel_confirmation on.
Simulates the increment of an authorization by a card acquirer. An authorization can be incremented multiple times.
The amount of the increment in minor units in the card authorization's currency.
The identifier of the Card Payment to create a increment on.
The identifier of the Event Subscription to use. If provided, will override the default real time event subscription. Because you can only create one real time decision event subscription, you can use this field to route events to any specified event subscription for testing purposes.
Simulates refunding a card transaction. The full value of the original sandbox transaction is refunded.
The identifier for the Transaction to refund. The Transaction's source must have a category of card_settlement.
Simulates the reversal of an authorization by a card acquirer. An authorization can be partially reversed multiple times, up until the total authorized amount. Marks the pending transaction as complete if the authorization is fully reversed.
The amount of the reversal in minor units in the card authorization's currency. This defaults to the authorization amount.
The identifier of the Card Payment to create a reversal on.
Simulates the settlement of an authorization by a card acquirer. After a card authorization is created, the merchant will eventually send a settlement. This simulates that event, which may occur many days after the purchase in production. The amount settled can be different from the amount originally authorized, for example, when adding a tip to a restaurant bill.
The amount to be settled. This defaults to the amount of the Pending Transaction being settled.
The identifier of the Card to create a settlement on.
The identifier of the Pending Transaction for the Card Authorization you wish to settle.