direct
connections to another. P2P payments must be individually authorized by the sender within 10 minutes of creation, using a verification code sent to their mobile device. Once committed, P2P payments are initiated immediately, and cannot be canceled.
payment.debit
permission from the source Account Connection and the payment.credit
permission from the destination Account Connection. Since peer to peer implementations typically allow free money flow to/from all peers, we recommend requesting both permissions from all users.POST
/p2pPayment from ${sourceFullName} to ${destinationFullName}
Payment from ${sourceFullName} to ${destinationFullName}
Status | Description |
---|---|
created | Initial status after object creation. Requires Commit P2P method to be executed. |
pending | P2P has been committed, but payment is not complete. |
sent | The payment was completed and the amount is now available in the destination account. |
error | The payment encountered an error during processing. The reasons a payment might be set to error include non-sufficient funds, suspected fraud, or failed validation. |