Skip to content

chore(docs): update state description on Card #278

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stainless-app merged 1 commit into from
Aug 19, 2024
Merged

chore(docs): update state description on Card #278

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 20 additions & 20 deletions lithic-java-core/src/main/kotlin/com/lithic/api/models/Card.kt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -148,11 +148,11 @@ private constructor(
* provisioned pending manufacturing and fulfillment. Cards in this state can accept
* authorizations for e-commerce purchases, but not for "Card Present" purchases where the
* physical card itself is present.
* - `PENDING_ACTIVATION` - Each business day at 2pm Eastern Time Zone (ET), cards of type
* `PHYSICAL` in state `PENDING_FULFILLMENT` are sent to the card production warehouse and
* updated to state `PENDING_ACTIVATION` . Similar to `PENDING_FULFILLMENT`, cards in this
* state can be used for e-commerce transactions. API clients should update the card's state
* to `OPEN` only after the cardholder confirms receipt of the card.
* - `PENDING_ACTIVATION` - At regular intervals, cards of type `PHYSICAL` in state
* `PENDING_FULFILLMENT` are sent to the card production warehouse and updated to state
* `PENDING_ACTIVATION` . Similar to `PENDING_FULFILLMENT`, cards in this state can be used
* for e-commerce transactions. API clients should update the card's state to `OPEN` only
* after the cardholder confirms receipt of the card.
*
* In sandbox, the same daily batch fulfillment occurs, but no cards are actually manufactured.
*/
Expand Down Expand Up @@ -274,11 +274,11 @@ private constructor(
* provisioned pending manufacturing and fulfillment. Cards in this state can accept
* authorizations for e-commerce purchases, but not for "Card Present" purchases where the
* physical card itself is present.
* - `PENDING_ACTIVATION` - Each business day at 2pm Eastern Time Zone (ET), cards of type
* `PHYSICAL` in state `PENDING_FULFILLMENT` are sent to the card production warehouse and
* updated to state `PENDING_ACTIVATION` . Similar to `PENDING_FULFILLMENT`, cards in this
* state can be used for e-commerce transactions. API clients should update the card's state
* to `OPEN` only after the cardholder confirms receipt of the card.
* - `PENDING_ACTIVATION` - At regular intervals, cards of type `PHYSICAL` in state
* `PENDING_FULFILLMENT` are sent to the card production warehouse and updated to state
* `PENDING_ACTIVATION` . Similar to `PENDING_FULFILLMENT`, cards in this state can be used
* for e-commerce transactions. API clients should update the card's state to `OPEN` only
* after the cardholder confirms receipt of the card.
*
* In sandbox, the same daily batch fulfillment occurs, but no cards are actually manufactured.
*/
Expand Down Expand Up @@ -680,11 +680,11 @@ private constructor(
* provisioned pending manufacturing and fulfillment. Cards in this state can accept
* authorizations for e-commerce purchases, but not for "Card Present" purchases where the
* physical card itself is present.
* - `PENDING_ACTIVATION` - Each business day at 2pm Eastern Time Zone (ET), cards of type
* `PHYSICAL` in state `PENDING_FULFILLMENT` are sent to the card production warehouse and
* updated to state `PENDING_ACTIVATION` . Similar to `PENDING_FULFILLMENT`, cards in this
* state can be used for e-commerce transactions. API clients should update the card's
* state to `OPEN` only after the cardholder confirms receipt of the card.
* - `PENDING_ACTIVATION` - At regular intervals, cards of type `PHYSICAL` in state
* `PENDING_FULFILLMENT` are sent to the card production warehouse and updated to state
* `PENDING_ACTIVATION` . Similar to `PENDING_FULFILLMENT`, cards in this state can be
* used for e-commerce transactions. API clients should update the card's state to `OPEN`
* only after the cardholder confirms receipt of the card.
*
* In sandbox, the same daily batch fulfillment occurs, but no cards are actually
* manufactured.
Expand All @@ -700,11 +700,11 @@ private constructor(
* provisioned pending manufacturing and fulfillment. Cards in this state can accept
* authorizations for e-commerce purchases, but not for "Card Present" purchases where the
* physical card itself is present.
* - `PENDING_ACTIVATION` - Each business day at 2pm Eastern Time Zone (ET), cards of type
* `PHYSICAL` in state `PENDING_FULFILLMENT` are sent to the card production warehouse and
* updated to state `PENDING_ACTIVATION` . Similar to `PENDING_FULFILLMENT`, cards in this
* state can be used for e-commerce transactions. API clients should update the card's
* state to `OPEN` only after the cardholder confirms receipt of the card.
* - `PENDING_ACTIVATION` - At regular intervals, cards of type `PHYSICAL` in state
* `PENDING_FULFILLMENT` are sent to the card production warehouse and updated to state
* `PENDING_ACTIVATION` . Similar to `PENDING_FULFILLMENT`, cards in this state can be
* used for e-commerce transactions. API clients should update the card's state to `OPEN`
* only after the cardholder confirms receipt of the card.
*
* In sandbox, the same daily batch fulfillment occurs, but no cards are actually
* manufactured.
Expand Down