Payments on Fiat Republic can be both internal and external. Internal payments are created between 2 Fiat Accounts while external payments are created from a Fiat or Virtual Account to a Payee.
Payments Object
Attribute | Description | Format/Enum |
---|---|---|
id string | Unique identifier of the payment. | e.g. |
fromId | Identifier of the source entity of the payment, which will usually belong to a Fiat Account, Virtual Account or Payer. | e.g. |
toId | Identifier of the destination entity of the payment, which will usually belong to a Fiat Account, Virtual Account or Payee. | e.g. |
direction | Direction of the payment. |
|
reference | Reference received or sent with the Payment. | Payment reference must consist of at least 6 alphanumeric characters that are not all the same. Can contain special characters include space, hyphen(-), full stop (.), ampersand(&), and forward slash (/), which are uncounted. Total of all characters must be less than:
|
effectiveReference | Displays the effective reference applied when payment was sent. |
|
amount | Amount of the payment in 2 decimal places. | e.g. |
currency | Currency of the payment. | Three-letter ISO 4217 code e.g. |
paymentScheme | The payment scheme used for the payment. |
|
status | Status of the payment. |
|
paymentReturnId | Unique identifier of the return associated with the payment (if the payment was returned). | e.g. |
memberReview | Decision taken by a Member on a Payment (Payin) if it went through the Member Review flow. |
|
createdAt | Epoch timestamp at which the object was created. | e.g. |
updatedAt | Epoch timestamp at which the object was last updated. | e.g. |
metadata | Additional data in JSON | See Metadata for more information. |
When you create an external payment from a Fiat or Virtual Account to a Payee, the amount will be reserved until the Payment is completed. Upon completion, the reserved amount will be debited and a transaction will be posted on the relevant Fiat Account.
Payment Schemes
You can find full list of available payment schemes here Currencies and Schemes
Payment Statuses
Payment Status | Description |
---|---|
| The payment has been created and will be submitted to the banking provider subject to compliance checks. |
| The payment has been submitted to the banking provider for execution. |
| The payment has been created but some automated compliance checks are not yet complete. Our compliance team may reach out to you for additional information on such payments. For incoming payments, this provides visibility of funds having been received but not yet credited on the relevant Fiat Account. |
| The payment has been created successfully and is subject to the process of 4 eyes check |
| The payment has been successfully processed by the banking provider. At this point, the payment has been instructed to the scheme and does not necessarily mean that it has been received by the Payee. Processing times vary depending on scheme. |
| Payouts that were returned by the Payee's bank and we were able to successfully identify and reconcile the payment as a return. If a previously Completed payment is Returned, a separate credit transaction of type |
| The payment was rejected by Fiat Republic for compliance reasons. |
| There was an issue with the Payment and it was failed either by Fiat Republic or by the banking provider. This can be for reasons such as incorrect Payee bank details, Payee's bank account being closed etc. |
| Due to falling outside of my risk tolerance, the payment is currently awaiting review before it can be completed and a transaction is created on the Fiat Account. |