Create a transaction
Create a transaction
Authorizations
API Key authentication. Use "Bearer YOUR_API_KEY".
Body
The ID of the customer the transaction is for.
The payment method types allowed for this transaction.
1autogiro, bacs_debit, card, card_present, bank_transfer, direct_transfer, gbp_credit_transfer, pay_by_bank, sepa_debit The ID of the application the transaction is for.
The application payment type. Only allowed if the supplied application is open.
advance_rent, deposit, holding_fee, partial_payment, null The amount to charge. Should be a positive integer in the smallest currency unit (e.g. 100 for £1.00). The amount is required if you do not supply an application and application_payment_type.
1 <= x <= 99999900Controls when the funds will be captured from the customer.
automatic, manual Set to true to attempt to confirm this transaction immediately.
Three-letter ISO currency code, in lowercase. Must be a supported currency.
gbp, eur, usd, null A hash containing information about the customer balance options.
An arbitrary string attached to the object. Often useful for displaying to users.
The ID of the invoice this transaction is intended to pay.
Set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format.
Set to true to indicate the customer is not in the checkout flow.
The ID of the payment method to use for this transaction.
The reporting type of the transaction. Only allowed if you don't supply an application ID.
advance_rent, charge, deposit, holding_fee, rent, null The URL to redirect the user to if the transaction requires additional action to complete.
Whether to send a receipt email to the customer after the transaction succeeds.
The statement descriptor that will appear on customers bank statement. Only allowed if you don't supply an application payment type.
The ID of the unit. Only allowed if you don't supply an application ID.
The workspace the transaction belongs to.
Response
Returns the created transaction.
Unique identifier for the object.
Time at which the object was created. Measured in seconds since the Unix epoch.
transaction Adaptive pricing information, if enabled for this transaction.
The amount of the transaction in the smallest currency unit (e.g. cents).
The ID of the application the transaction is associated with.
The balance transaction associated with this transaction.
Controls when the funds will be captured from the customer.
automatic, manual, null The client secret used to complete the transaction on the client side.
The time at which the transaction was confirmed.
Cross-border payment information, if applicable.
Three-letter ISO currency code, in lowercase. Must be a supported currency.
The customer the transaction is for.
An arbitrary string attached to the object. Often useful for displaying to users.
The dispute associated with the transaction, if any.
The invoice the transaction was created to pay, if any.
The most recent payment error encountered when attempting the transaction.
The next action required to complete the transaction, if any.
- Option 1
- Option 2
- Option 3
- Option 4
The time at which the transaction was paid.
The payment method used or to be used to complete the transaction.
The payment method types allowed for this transaction.
The payment session associated with this transaction, if any.
Details of the amount and currency presented to the customer.
Details about the processing state of the transaction.
The URL of the hosted receipt for this transaction.
The reporting type used to categorize this transaction.
The status of the transaction.
requires_payment_method, requires_confirmation, requires_action, processing, canceled, succeeded A string identifier that groups together transactions for a single transfer.
The account that the object belongs to. Only returned if the request is made with a valid Yorlet-Context header.
Only returned if the object has been deleted.
The amount that has been refunded for this transaction.
Whether the transaction has been disputed by the customer.
Set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format.
Whether the transaction has been fully refunded.