-
Notifications
You must be signed in to change notification settings - Fork 7
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.
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
Feature/checkout expiration #97
Changes from 5 commits
eed0035
90d6bdb
21a84e7
fa504fd
8355c8b
51e7fba
6c16986
3489248
360369f
aeb9625
4bd0055
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
export const description = | ||
'La propiedad expiration se utiliza para definir el período durante el cual una sesión puede ser procesada' | ||
|
||
# Fecha de expiración | ||
|
||
Cuando se envía la propiedad `expiration` en la creación de una sesión esta define la fecha límite en la que una sesión debe completarse. El usuario debe finalizar el proceso antes de que se alcance esta fecha. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Lo mismo aplicaría aquí no?
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Necesitamos agregar una aclaración de que no necesariamente se debe finalizar, pues los pagos pendientes o cash siguen activos no? |
||
|
||
- **Formato Requerido**: La propiedad expiration debe ser un string en formato de timestamp válido conforme al estándar `ISO 8601`. | ||
Ejemplo: 2023-07-17T13:12:44-05:00. | ||
- **Tiempo Mínimo**: La fecha y hora establecidas en expiration deben estar al menos a **5 minutos** después del momento en que se crea la sesión. | ||
|
||
<Note> | ||
La propiedad expiration es opcional. Si no se proporciona, el sistema asignará automáticamente un tiempo de expiración predeterminado de **30 minutes** desde la creación de la sesión. | ||
</Note> | ||
|
||
```json | ||
{ | ||
"locale": "es_CO", | ||
"auth": ... | ||
"payment": { | ||
... | ||
} | ||
"expiration": "2024-09-03T12:23:39-05:00", | ||
... | ||
} | ||
``` |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
export const description = | ||
'The expiration property is used to define the period during which a session can be processed' | ||
|
||
# Expiration Date | ||
When the `expiration` property is sent during session creation, it defines the deadline by which a session must be completed. The user must finish the process before this date is reached. | ||
|
||
- **Required Format**: The expiration property must be a string in a valid timestamp format according to the `ISO 8601` standard. | ||
Example: 2023-07-17T13:12:44-05:00. | ||
- **Minimum Time**: The date and time specified in expiration must be at least **5 minutes** after the session is created. | ||
|
||
<Note> | ||
The `expiration` property is optional. If not provided, the system will automatically assign a default expiration time of **30 minutes** from the session creation. | ||
</Note> | ||
|
||
```json | ||
{ | ||
"locale": "es_CO", | ||
"auth": ... | ||
"payment": { | ||
... | ||
} | ||
"expiration": "2024-09-03T12:23:39-05:00", | ||
... | ||
} | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
La propiedad no es
payment.expiration
si te fijas la propiedad esexpiration
en la raiz.Lo que me hace pensar que los changelog deberían llevar el nombre de la entidad o estructura que se está cambiando. Para este caso es el
CreateSessionRequest
o al menos así lo hemos llamado en la documentación algunas veces.Mi propuesta: