Cards may operate on credit, debit, or prepaid BINs. They’ll immediately work for online purchases after you create them. All cards work on a good funds model, and maintain a maximum limit of 100% of the Account’s available balance at the time of transaction. Funds are deducted from the Account upon transaction settlement.
The identifier for the account this card belongs to.
Controls that restrict how this card can be used.
The Card’s billing address.
The Bank Identification Number (BIN) of the Card.
The name of the cardholder. Used to respond to Account Name Inquiry requests from acquirers in Card Validations.
The ISO 8601 date and time at which the Card was created.
The card’s description for display purposes.
The contact information used in the two-factor steps for digital wallet card creation. At least one field must be present to complete the digital wallet steps.
The identifier for the entity associated with this card.
The month the card expires in M format (e.g., August is 8).
The year the card expires in YYYY format (e.g., 2025).
The card identifier.
The idempotency key you chose for this object. This value is unique across Increase and is used to ensure that a request is only processed once. Learn more about idempotency.
The last 4 digits of the Card’s Primary Account Number.
Completed renewals of this Card, sorted by renewed_at in ascending order. Each renewal records the expiration date the Card had before it was renewed.
Details about the Card this Card replaces, if it was created as a replacement.
This indicates if payments can be made with the card.
A constant representing the object’s type. For this resource it will always be card.
Filter Cards to ones belonging to the specified Account.
Filter Cards by status. For GET requests, this should be encoded as a comma-delimited string, such as ?in=one,two,three.
Filter records to the one with the specified idempotency_key you chose for that object. This value is unique across Increase and is used to ensure that a request is only processed once. Learn more about idempotency.
The Account the card should belong to.
Controls that restrict how this card can be used.
The card’s billing address.
The name of the cardholder. Used to respond to Account Name Inquiry requests from acquirers in Card Validations.
The description you choose to give the card.
The contact information used in the two-factor steps for digital wallet card creation. To add the card to a digital wallet, you may supply an email or phone number with this request. Otherwise, subscribe and then action a Real Time Decision with the category digital_wallet_token_requested or digital_wallet_authentication_requested.
The Entity the card belongs to. You only need to supply this in rare situations when the card is not for the Account holder.
Details about the Card this Card replaces. Supply this when issuing a new Card to take over from an existing one. The replaced Card is not canceled.
The card identifier.
Controls that restrict how this card can be used.
The card’s updated billing address.
The description you choose to give the card.
The contact information used in the two-factor steps for digital wallet card creation. At least one field must be present to complete the digital wallet steps.
The Entity the card belongs to. You only need to supply this in rare situations when the card is not for the Account holder.
The status to update the Card with.
Create an iframe URL for a Card to display the card details. More details about styling and usage can be found in the documentation.
The identifier of the Card to create an iframe for.
The identifier of the Physical Card to create an iframe for. This will inform the appearance of the card rendered in the iframe.
Create a short-lived token that authorizes Card Elements to render the details of a Card in your frontend. Mint the token on your server and pass it to the browser; the token is valid for one hour and is scoped to a single Card.
The identifier of the Card to mint a details token for.
Sensitive details for a Card include the primary account number, expiration, card verification code, and PIN.
The identifier of the Card to retrieve details for.
Renew a Card in place. The Card keeps its identifier, card number, PIN, and Physical Cards, and receives a new expiration date in the current month four years from now along with a new verification code, which the Card’s details will return afterwards. Physical Cards that have already shipped keep working until they are canceled.
The identifier of the Card to renew.
The identifier of the Card to update the PIN for.
The 4-digit PIN for the card, for use with ATMs.