Flow

Request a Payment Session #

Creates a payment session for Flow. The values you provide in the request will be used to determine the payment methods available to Flow. Some payment methods may require you to provide specific values for certain fields. You must supply the unmodified response body when you initialize Flow.

Authorizations

bearer

#
HTTP: bearer #

HTTP Authorization Scheme: bearer

Bearer format: JWT

header Parameters #
AuthorizationrequiredstringBearer token (API Key or OAuth2 Access Token).
Request Body schema: application/json #

Request body for creating a Flow payment session.

amountrequirednumber >= 0 The payment amount in minor units. Provide 0 to perform a card verification.
currencyrequiredstring = 3 characters The three-letter ISO currency code.
billingrequiredobjectThe billing details.
success_urlrequiredstring <= 1024 characters Overrides the default success redirect URL for payment methods that require a redirect.
failure_urlrequiredstring <= 1024 characters Overrides the default failure redirect URL for payment methods that require a redirect.
payment_typestring Default: “Regular” Enum:”Regular””Recurring””MOTO””Installment””Unscheduled”Must be specified for card-not-present (CNP) payments.
billing_descriptorobjectA description of the purchase, displayed on the customer’s statement.
referencestring <= 50 characters A reference to identify the payment (max 50 chars, Amex: 30, iDEAL: 35, Benefit: unique alphanumeric).
descriptionstring <= 100 characters A description for the payment (max 100 chars).
customerobjectThe customer’s details. Required if source.type is tamara.
shippingobjectThe shipping details.
recipientobjectInformation about the recipient of the payment’s funds.
processingobjectProcessing options.
instructionobjectDetails about the payment instruction.
processing_channel_idstring^(pc)_(\w{26})$The processing channel to use for the payment.
expires_onstringA timestamp specifying when the PaymentSession should expire, as an ISO 8601 code.
payment_method_configurationobjectConfigurations for payment method-specific settings.
enabled_payment_methodsArray of stringsSpecifies which payment method options to present to the customer.
disabled_payment_methodsArray of stringsSpecifies which payment method options to not present to the customer.
itemsArray of objectsThe line items in the order.
amount_allocationsArray of objectsThe sub-entities that the payment is being processed on behalf of.
riskobjectConfigures the risk assessment performed during payment processing.
customer_retryobjectConfiguration for asynchronous retries.
display_namestring <= 255 characters The merchant’s display name.
metadataobjectAllows you to store additional information about a transaction with custom fields (up to 18 fields, 255 chars each).
localestring Default: “en-GB”Creates a translated version of the page in the specified language.
3dsobjectInformation required for 3D Secure authentication payments.
senderobjectThe sender of the payment.
captureboolean Default: trueSpecifies whether to capture the payment, if applicable.
capture_onstringA timestamp specifying when to capture the payment, as an ISO 8601 code.
Responses #
201 A Payment Session.
Response Schema: application/json #
idrequiredstringThe Payment Session unique identifier.
statusstringThe status of the payment session.
payment_idstringThe payment identifier associated with the session.
amountnumberThe payment amount in minor units.
currencystringThe three-letter ISO currency code.
referencestringA reference to identify the payment.
descriptionstringA description for the payment.
expires_onstringA timestamp specifying when the PaymentSession should expire, as an ISO 8601 code.
customerobjectThe customer’s details.
billingobjectThe billing details.
productsArray of objectsThe products in the order.
payment_session_tokenstringA unique token representing the payment session, which you must provide when you initialize Flow.
payment_session_secretstringThe secret used by Flow to authenticate payment session requests.
_linksrequiredobjectThe links related to the Payment Session.

401 Unauthorized

422 Invalid data was sent.
Response Schema: application/json #
request_idrequiredstringThe unique request identifier.
error_typerequiredstringThe error type.
error_codesrequiredArray of stringsThe error codes.
429 Too many requests.
Response Schema: application/json #
request_idrequiredstringThe unique request identifier.
error_typerequiredstringThe error type.
error_codesrequiredArray of stringsThe error codes.

502 Bad gateway

Submit a Payment Session Payment #

Submit a payment attempt for a payment session. Request a payment via your created payment session. This request works with the Flow handleSubmit callback, where you can perform a customized payment submission. You must send the unmodified response body as the response of the handleSubmit callback.

Authorizations

bearer

#
HTTP: bearer #

HTTP Authorization Scheme: bearer

Bearer format: JWT

header Parameters #
AuthorizationrequiredstringBearer token (API Key or OAuth2 Access Token).
Request Body schema: application/json #

Request body for submitting a payment session payment.

session_datarequiredstringA unique token representing the additional customer data captured by Flow, as received from the handleSubmit callback. Do not log or store this value.
amountrequirednumber >= 0 The payment amount in minor units. Provide 0 to perform a card verification.
referencestring <= 50 characters A reference to identify the payment (max 50 chars, Amex: 30, iDEAL: 35, Benefit: unique alphanumeric).
itemsArray of objectsThe line items in the order.
3dsobjectInformation required for 3D Secure authentication payments.
ip_addressstring <= 45 characters The customer’s IP address. Only IPv4 and IPv6 addresses are accepted.
Responses #
201 Payment processed successfully
Response Schema: application/json #
idrequiredstringThe payment identifier.
statusrequiredstringThe payment’s status.
typerequiredArray of stringsThe payment method name.
202 Payment asynchronous or further action required
Response Schema: application/json #
idrequiredstringThe payment identifier.
statusrequiredstringThe payment’s status.
typerequiredstringThe payment method name.
actionrequiredobjectInstruction for further payment action.

401 Unauthorized

422 Invalid data was sent.
Response Schema: application/json #
request_idrequiredstringThe unique request identifier.
error_typerequiredstringThe error type.
error_codesrequiredArray of stringsThe error codes.
429 Too many requests or duplicate request detected
Response Schema: application/json #
request_idrequiredstringThe unique request identifier.
error_typerequiredstringThe error type.
error_codesrequiredArray of stringsThe error codes.

502 Bad gateway

Get Payment Session Details #

Returns the details of the payment session with the specified identifier string.

Authorizations

bearer

#
HTTP: bearer #

HTTP Authorization Scheme: bearer

Bearer format: JWT

path Parameters #
idrequiredstring
header Parameters #
AuthorizationrequiredstringBearer token (API Key or OAuth2 Access Token).
200 Payment session retrieved successfully
Response Schema: application/json #
idrequiredstringThe Payment Session unique identifier.
statusstringThe status of the payment session.
payment_idstringThe payment identifier associated with the session.
amountnumberThe payment amount in minor units.
currencystringThe three-letter ISO currency code.
referencestringA reference to identify the payment.
descriptionstringA description for the payment.
expires_onstringA timestamp specifying when the PaymentSession should expire, as an ISO 8601 code.
customerobjectThe customer’s details.
billingobjectThe billing details.
productsArray of objectsThe products in the order.
payment_session_tokenstringA unique token representing the payment session, which you must provide when you initialize Flow.
payment_session_secretstringThe secret used by Flow to authenticate payment session requests.
_linksrequiredobjectThe links related to the Payment Session.

401 Unauthorized
404 Session not found

Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll to Top